teammem 0.1.0__tar.gz

teammem-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

teammem-0.1.0/PKG-INFO

@@ -0,0 +1,241 @@
+Metadata-Version: 2.4
+Name: teammem
+Version: 0.1.0
+Summary: Local-first team activity ledger, member-bundle importer, and Markdown renderer
+Author: Team Memory Agent contributors
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/xiongxhc/team-memory-agent
+Project-URL: Documentation, https://github.com/xiongxhc/team-memory-agent#readme
+Project-URL: Issues, https://github.com/xiongxhc/team-memory-agent/issues
+Project-URL: Repository, https://github.com/xiongxhc/team-memory-agent
+Keywords: agents,knowledge-management,local-first,team-memory
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Office/Business
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyYAML>=6.0
+Requires-Dist: requests>=2.31
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Dynamic: license-file
+
+# Team Memory Agent
+
+Team Memory Agent turns scattered team activity into a local, queryable event
+ledger and regenerated Markdown reports. It combines central signals such as forge
+commits and shared project-channel messages with member-reviewed local highlights.
+
+The privacy boundary is simple: MemberKit prepares a JSON bundle locally, the
+member reviews it, and nothing is transmitted until that member explicitly runs
+`memberkit push`. Scheduled runs create drafts and reminders only.
+
+## Components
+
+| Component | Installed by | Purpose |
+|---|---|---|
+| `teammem` | Hub operator | Collect, import, query, and render |
+| `teammem-memberkit` | Individual member | Draft, review, and push selected highlights |
+| `teammem-bundle/v1` | Both packages | Frozen JSON protocol |
+
+MemberKit is a standalone command-line package, not a skill. Members install only
+`teammem-memberkit`; they do not clone this repository or install the hub.
+
+## Member quick start
+
+### 1. Get the two team-specific values
+
+Ask the hub operator for:
+
+- your roster slug, such as `alex`;
+- the Git URL of the team-memory inbox, plus permission to push to it.
+
+MemberKit v0.1 reads local observations from
+[`claude-mem`](https://github.com/thedotmack/claude-mem). Its default database is
+`~/.claude-mem/claude-mem.db`. You also need Python 3.11 or newer, `pipx`, and Git.
+
+### 2. Install and configure
+
+Installing the package does not create a schedule or transmit anything.
+
+```bash
+pipx install teammem-memberkit
+memberkit setup
+```
+
+Setup asks for the roster slug and inbox Git URL. On macOS it then proposes a daily
+17:30 reminder in the member's local timezone: press Enter to accept, enter another
+`HH:MM`, or enter `no` to decline. The configuration is stored with user-only
+permissions at `~/.config/teammem/memberkit.env`.
+
+For unattended setup:
+
+```bash
+memberkit setup \
+  --member alex \
+  --inbox-url git@forge.example:team/team-memory-inbox.git \
+  --time 17:30
+```
+
+Use `--no-schedule` instead of `--time` to configure MemberKit without installing
+the macOS schedule.
+
+### 3. Review before sharing
+
+The schedule prepares a local draft and shows a reminder. It never pushes. Review
+today's draft:
+
+```bash
+memberkit review
+```
+
+To remove private items, edit the `events` list in
+`~/.memberkit/out/bundle-<member>-<YYYY-MM-DD>.json`, save valid JSON, and review
+again. `journal_md` is only a preview and is regenerated from the reviewed event
+list when pushing.
+
+Share the reviewed date, or dismiss it without sharing:
+
+```bash
+memberkit push --date YYYY-MM-DD
+memberkit dismiss --date YYYY-MM-DD
+```
+
+The date defaults to today for `draft`, `review`, `push`, and `dismiss`. Removed or
+dismissed events remain excluded from later catch-up drafts.
+
+### Schedule behavior
+
+A scheduled run checks yesterday and today, preserving every event's original local
+calendar date. With the default 17:30 schedule, work from 17:30–23:59 is discovered
+the next day but remains in the earlier day's catch-up draft. Work at or after
+midnight belongs to the next calendar day. Older unfinished dates remain in later
+reminders.
+
+```bash
+memberkit schedule status
+memberkit schedule install --time 17:30
+memberkit schedule remove
+memberkit scheduled-run
+```
+
+Automatic schedule installation currently supports macOS launchd. Other platforms
+can schedule the portable `memberkit scheduled-run` command. If an edited draft is
+invalid JSON, a scheduled run leaves it untouched and keeps reminding the member
+to repair it. To discard a malformed draft, delete that local draft file before
+running `memberkit dismiss --date YYYY-MM-DD`.
+
+See the complete
+[MemberKit guide](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/member-guide.md)
+for upgrades, troubleshooting, files created locally, and safe removal.
+
+## Hub quick start
+
+The hub operator manages the central collectors, roster, inbox importer, ledger,
+and rendered views. Install the published command in an isolated environment:
+
+```bash
+pipx install teammem
+mkdir -p ~/.config/teammem
+curl -fsSL \
+  https://raw.githubusercontent.com/xiongxhc/team-memory-agent/master/config/roster.example.yaml \
+  -o ~/.config/teammem/roster.yaml
+curl -fsSL \
+  https://raw.githubusercontent.com/xiongxhc/team-memory-agent/master/config/projects.example.yaml \
+  -o ~/.config/teammem/projects.yaml
+```
+
+Edit both configuration files before collecting or importing data. Operators who
+are developing adapters or running from a pinned checkout can instead use:
+
+```bash
+git clone https://github.com/xiongxhc/team-memory-agent.git
+cd team-memory-agent
+python3 -m venv .venv
+.venv/bin/pip install -e .
+cp config/roster.example.yaml config/roster.yaml
+cp config/projects.example.yaml config/projects.yaml
+```
+
+Import reviewed bundles into a local ledger:
+
+```bash
+TEAMMEM_DB=ledger.db TEAMMEM_CONFIG_DIR=~/.config/teammem \
+  teammem import-bundles \
+    --inbox inbox \
+    --archive archive \
+    --quarantine quarantine
+```
+
+Render Markdown views:
+
+```bash
+TEAMMEM_DB=ledger.db TEAMMEM_CONFIG_DIR=~/.config/teammem TEAMMEM_VAULT=vault \
+  teammem render
+```
+
+GitLab and Feishu collectors are optional. LLM-backed synthesis is optional; the
+ledger, bundle importer, queries, and deterministic renderer work without it.
+
+The operator should create a private inbox Git repository, grant each member push
+access, and give each member an inbox URL and roster slug. Import from a disposable
+export of the inbox, not directly from its Git working tree, because accepted
+files are consumed from the import directory. See
+[deployment](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/deployment.md)
+for the complete operator and MemberKit lifecycle.
+
+Upgrade or uninstall the packaged command with:
+
+```bash
+pipx upgrade teammem
+pipx uninstall teammem
+```
+
+Uninstalling the command does not remove operator-owned configuration, ledgers,
+archives, quarantine records, or rendered views.
+
+## Principles
+
+- The SQLite ledger is truth; Markdown output is disposable and regenerated.
+- Import is idempotent per attributed event.
+- Unknown central identities are surfaced; unknown MemberKit identities are
+  quarantined.
+- Shared-channel collection requires a visibly present integration.
+- Raw local databases, direct messages, and arbitrary files never enter a bundle.
+- This project provides work visibility, not employee scoring or performance
+  evaluation.
+
+See
+[architecture](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/architecture.md),
+[privacy](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/privacy.md),
+[deployment](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/deployment.md),
+the
+[MemberKit guide](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/member-guide.md),
+and the
+[`teammem-bundle/v1` contract](https://github.com/xiongxhc/team-memory-agent/blob/master/schemas/teammem-bundle-v1.md).
+
+## Development
+
+```bash
+python3 -m venv .venv
+.venv/bin/pip install -e '.[dev]'
+.venv/bin/pip install -e packages/memberkit
+.venv/bin/pytest -q tests packages/memberkit/tests
+./scripts/check-public.sh
+```
+
+Before publication, the extracting operator should also provide a private regular
+expression containing origin-specific organization and member identifiers without
+committing it:
+
+```bash
+TEAMMEM_PUBLIC_DENY_REGEX='<private-regex>' ./scripts/check-public.sh
+```
+
+This project is licensed under Apache-2.0. The code owner authorized publication
+under that license on 2026-07-27.

teammem-0.1.0/README.md

@@ -0,0 +1,214 @@
+# Team Memory Agent
+
+Team Memory Agent turns scattered team activity into a local, queryable event
+ledger and regenerated Markdown reports. It combines central signals such as forge
+commits and shared project-channel messages with member-reviewed local highlights.
+
+The privacy boundary is simple: MemberKit prepares a JSON bundle locally, the
+member reviews it, and nothing is transmitted until that member explicitly runs
+`memberkit push`. Scheduled runs create drafts and reminders only.
+
+## Components
+
+| Component | Installed by | Purpose |
+|---|---|---|
+| `teammem` | Hub operator | Collect, import, query, and render |
+| `teammem-memberkit` | Individual member | Draft, review, and push selected highlights |
+| `teammem-bundle/v1` | Both packages | Frozen JSON protocol |
+
+MemberKit is a standalone command-line package, not a skill. Members install only
+`teammem-memberkit`; they do not clone this repository or install the hub.
+
+## Member quick start
+
+### 1. Get the two team-specific values
+
+Ask the hub operator for:
+
+- your roster slug, such as `alex`;
+- the Git URL of the team-memory inbox, plus permission to push to it.
+
+MemberKit v0.1 reads local observations from
+[`claude-mem`](https://github.com/thedotmack/claude-mem). Its default database is
+`~/.claude-mem/claude-mem.db`. You also need Python 3.11 or newer, `pipx`, and Git.
+
+### 2. Install and configure
+
+Installing the package does not create a schedule or transmit anything.
+
+```bash
+pipx install teammem-memberkit
+memberkit setup
+```
+
+Setup asks for the roster slug and inbox Git URL. On macOS it then proposes a daily
+17:30 reminder in the member's local timezone: press Enter to accept, enter another
+`HH:MM`, or enter `no` to decline. The configuration is stored with user-only
+permissions at `~/.config/teammem/memberkit.env`.
+
+For unattended setup:
+
+```bash
+memberkit setup \
+  --member alex \
+  --inbox-url git@forge.example:team/team-memory-inbox.git \
+  --time 17:30
+```
+
+Use `--no-schedule` instead of `--time` to configure MemberKit without installing
+the macOS schedule.
+
+### 3. Review before sharing
+
+The schedule prepares a local draft and shows a reminder. It never pushes. Review
+today's draft:
+
+```bash
+memberkit review
+```
+
+To remove private items, edit the `events` list in
+`~/.memberkit/out/bundle-<member>-<YYYY-MM-DD>.json`, save valid JSON, and review
+again. `journal_md` is only a preview and is regenerated from the reviewed event
+list when pushing.
+
+Share the reviewed date, or dismiss it without sharing:
+
+```bash
+memberkit push --date YYYY-MM-DD
+memberkit dismiss --date YYYY-MM-DD
+```
+
+The date defaults to today for `draft`, `review`, `push`, and `dismiss`. Removed or
+dismissed events remain excluded from later catch-up drafts.
+
+### Schedule behavior
+
+A scheduled run checks yesterday and today, preserving every event's original local
+calendar date. With the default 17:30 schedule, work from 17:30–23:59 is discovered
+the next day but remains in the earlier day's catch-up draft. Work at or after
+midnight belongs to the next calendar day. Older unfinished dates remain in later
+reminders.
+
+```bash
+memberkit schedule status
+memberkit schedule install --time 17:30
+memberkit schedule remove
+memberkit scheduled-run
+```
+
+Automatic schedule installation currently supports macOS launchd. Other platforms
+can schedule the portable `memberkit scheduled-run` command. If an edited draft is
+invalid JSON, a scheduled run leaves it untouched and keeps reminding the member
+to repair it. To discard a malformed draft, delete that local draft file before
+running `memberkit dismiss --date YYYY-MM-DD`.
+
+See the complete
+[MemberKit guide](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/member-guide.md)
+for upgrades, troubleshooting, files created locally, and safe removal.
+
+## Hub quick start
+
+The hub operator manages the central collectors, roster, inbox importer, ledger,
+and rendered views. Install the published command in an isolated environment:
+
+```bash
+pipx install teammem
+mkdir -p ~/.config/teammem
+curl -fsSL \
+  https://raw.githubusercontent.com/xiongxhc/team-memory-agent/master/config/roster.example.yaml \
+  -o ~/.config/teammem/roster.yaml
+curl -fsSL \
+  https://raw.githubusercontent.com/xiongxhc/team-memory-agent/master/config/projects.example.yaml \
+  -o ~/.config/teammem/projects.yaml
+```
+
+Edit both configuration files before collecting or importing data. Operators who
+are developing adapters or running from a pinned checkout can instead use:
+
+```bash
+git clone https://github.com/xiongxhc/team-memory-agent.git
+cd team-memory-agent
+python3 -m venv .venv
+.venv/bin/pip install -e .
+cp config/roster.example.yaml config/roster.yaml
+cp config/projects.example.yaml config/projects.yaml
+```
+
+Import reviewed bundles into a local ledger:
+
+```bash
+TEAMMEM_DB=ledger.db TEAMMEM_CONFIG_DIR=~/.config/teammem \
+  teammem import-bundles \
+    --inbox inbox \
+    --archive archive \
+    --quarantine quarantine
+```
+
+Render Markdown views:
+
+```bash
+TEAMMEM_DB=ledger.db TEAMMEM_CONFIG_DIR=~/.config/teammem TEAMMEM_VAULT=vault \
+  teammem render
+```
+
+GitLab and Feishu collectors are optional. LLM-backed synthesis is optional; the
+ledger, bundle importer, queries, and deterministic renderer work without it.
+
+The operator should create a private inbox Git repository, grant each member push
+access, and give each member an inbox URL and roster slug. Import from a disposable
+export of the inbox, not directly from its Git working tree, because accepted
+files are consumed from the import directory. See
+[deployment](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/deployment.md)
+for the complete operator and MemberKit lifecycle.
+
+Upgrade or uninstall the packaged command with:
+
+```bash
+pipx upgrade teammem
+pipx uninstall teammem
+```
+
+Uninstalling the command does not remove operator-owned configuration, ledgers,
+archives, quarantine records, or rendered views.
+
+## Principles
+
+- The SQLite ledger is truth; Markdown output is disposable and regenerated.
+- Import is idempotent per attributed event.
+- Unknown central identities are surfaced; unknown MemberKit identities are
+  quarantined.
+- Shared-channel collection requires a visibly present integration.
+- Raw local databases, direct messages, and arbitrary files never enter a bundle.
+- This project provides work visibility, not employee scoring or performance
+  evaluation.
+
+See
+[architecture](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/architecture.md),
+[privacy](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/privacy.md),
+[deployment](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/deployment.md),
+the
+[MemberKit guide](https://github.com/xiongxhc/team-memory-agent/blob/master/docs/member-guide.md),
+and the
+[`teammem-bundle/v1` contract](https://github.com/xiongxhc/team-memory-agent/blob/master/schemas/teammem-bundle-v1.md).
+
+## Development
+
+```bash
+python3 -m venv .venv
+.venv/bin/pip install -e '.[dev]'
+.venv/bin/pip install -e packages/memberkit
+.venv/bin/pytest -q tests packages/memberkit/tests
+./scripts/check-public.sh
+```
+
+Before publication, the extracting operator should also provide a private regular
+expression containing origin-specific organization and member identifiers without
+committing it:
+
+```bash
+TEAMMEM_PUBLIC_DENY_REGEX='<private-regex>' ./scripts/check-public.sh
+```
+
+This project is licensed under Apache-2.0. The code owner authorized publication
+under that license on 2026-07-27.