ildan-memforge 0.3.1__tar.gz

ildan_memforge-0.3.1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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.

ildan_memforge-0.3.1/PKG-INFO

@@ -0,0 +1,175 @@
+Metadata-Version: 2.4
+Name: ildan-memforge
+Version: 0.3.1
+Summary: MemForge: portable, agent-neutral persistent memory for coding agents (ILDAN).
+Author: ILDAN
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/ildan-ai/memforge
+Project-URL: Issues, https://github.com/ildan-ai/memforge/issues
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyYAML>=6.0
+Requires-Dist: watchdog>=4.0
+Provides-Extra: dlp
+Requires-Dist: detect-secrets>=1.5; extra == "dlp"
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: pip-audit>=2.7; extra == "dev"
+Dynamic: license-file
+
+# MemForge
+
+**Typed, git-native, dynamic memory for coding agents.** A markdown folder + a small spec + reference tooling. Works across Claude Code, Cursor, Aider, Codex, and GitHub Copilot Chat through thin adapters.
+
+> **Status: pre-1.0; external PRs paused.** Issues and Discussions are open. External pull requests are paused until the Contributor License Agreement infrastructure lands; the CLA flow will land in a v0.3.x patch release. See [CONTRIBUTING.md](./CONTRIBUTING.md). Security reports go through the private channel in [SECURITY.md](./SECURITY.md).
+
+## The gap MemForge fills
+
+Coding agents have static instruction surfaces (AGENTS.md, `.cursorrules`, `CONVENTIONS.md`, `.github/copilot-instructions.md`, Claude Code's auto-memory) for things you want the agent to read at the start of every session. They handle the "always-true" half well.
+
+What they don't handle: the **changing** half. The fact that you decided to use `bun` not `npm` last Tuesday. The reason you rejected the obvious database schema. The post-incident rule about not mocking the staging API. The seven things you've told four different agents the same way and are tired of repeating.
+
+That state belongs in *memory*: typed entries that the agent can read, write, audit, and version-control alongside the code. MemForge is the format for that memory and a small set of tools that keep it healthy.
+
+## What you get
+
+- **A folder of markdown files** with YAML frontmatter. Hand-editable, diffable, code-reviewable.
+- **Four memory types:** `user` (facts about the developer), `feedback` (rules they have given), `project` (state about ongoing work), `reference` (pointers to external systems).
+- **A `MEMORY.md` index** any agent loads at session start.
+- **Rollup subfolders** for topic clusters of five or more memories, so the index stays scannable.
+- **Audit + integrity tooling** that runs in CI: schema checks, link integrity, DLP scan, tamper-evident audit log.
+- **Adapters** for Claude Code, Cursor, Aider, OpenAI Codex, and GitHub Copilot Chat (VS Code).
+
+## 60-second install
+
+```bash
+pip install memforge   # publish target; not yet on PyPI as of v0.3.0
+# Or, until then:
+pip install git+https://github.com/ildan-ai/memforge.git
+```
+
+Pick a folder for your memory. The defaults the tooling assumes:
+
+```
+~/.claude/global-memory/                          # cross-project rules
+~/.claude/projects/<USER>-claude-projects/memory/ # per-cwd state
+```
+
+Other layouts work too; the tooling takes a `--path` argument everywhere.
+
+## A memory file, end-to-end
+
+```markdown
+---
+name: Use bun, not npm
+description: Bun is the package manager for this monorepo
+type: feedback
+tags: [topic:tooling, topic:javascript]
+status: active
+created: 2026-04-12
+---
+
+When installing or running scripts in this repo, use `bun` and `bunx`. Lockfile is `bun.lockb`.
+
+**Why:** the workspace setup at `apps/web/package.json` relies on bun's workspace resolver; npm pulls a slightly different dependency tree and the build fails downstream.
+
+**How to apply:** any time you reach for `npm install`, `npx`, or a `package-lock.json`, stop and use bun instead. If a script in the README still says `npm run`, treat that as a docs bug, not a directive.
+```
+
+That file is the unit. Every tool, every adapter, every check operates on files of exactly this shape.
+
+## When MemForge is the right tool
+
+- You move between coding agents and want them to share the same notes.
+- You want memory entries reviewable in pull requests, like code.
+- You want the operator to *see* what the agent has written about them and edit it freely.
+- You want CI gates on memory hygiene (broken links, secret leakage, schema drift).
+
+## When it is not
+
+- **Not a vector database.** No embeddings, no similarity search at runtime. Use `mem0` or `letta` if that is the shape you need.
+- **Not a secrets store.** The DLP scanner refuses files that look like they leak credentials, but the format is human-readable plain text. Keep secrets in a vault.
+- **Not a runtime memory layer.** MemForge is the *file format and the discipline*, not a service. Adapters load files into agent context at session start; nothing runs continuously.
+- **Not a replacement for AGENTS.md.** AGENTS.md is the README for agents (static, repo-level, project setup). MemForge is the working notebook (dynamic, evolving, often per-developer). They coexist.
+
+## How it compares
+
+| | **MemForge** | mem0 | letta | `.cursorrules` / `AGENTS.md` |
+|---|---|---|---|---|
+| Storage | Markdown files in git | Hosted vector store | Hosted agent state | Single text file |
+| Typed entries | Yes (4 types + status) | No | Partial | No |
+| Cross-agent | Yes (adapters) | Per-SDK | Per-SDK | Per-agent |
+| Reviewable in PRs | Yes (diff = the file) | No (opaque store) | No | Yes |
+| Runtime cost | Zero (load at session start) | Per-query embedding cost | Per-query | Zero |
+| Best for | Long-lived rules + decisions | Conversational recall | Stateful agent loops | Project-level setup |
+
+The honest summary: if your agent is a long-running service that needs to remember a thousand things from yesterday's chat, you want a vector store. If your agent is a coding session that needs to remember the rules and decisions a human cares about across sessions, you want MemForge.
+
+## Architecture
+
+```mermaid
+flowchart LR
+    Dev[Developer] -->|edits| Folder[Memory folder<br/>markdown + YAML]
+    Folder -->|read at session start| AdapterCC[Claude Code adapter]
+    Folder -->|read at session start| AdapterCursor[Cursor adapter]
+    Folder -->|read at session start| AdapterAider[Aider adapter]
+    Folder -->|read at session start| AdapterCodex[Codex adapter]
+    Folder -->|read at session start| AdapterCopilot[Copilot Chat adapter]
+    AdapterCC --> Agent1[Claude Code]
+    AdapterCursor --> Agent2[Cursor]
+    AdapterAider --> Agent3[Aider]
+    AdapterCodex --> Agent4[OpenAI Codex]
+    AdapterCopilot --> Agent5[GitHub Copilot Chat]
+    Folder -->|CI gate| Tools[memory-audit<br/>memory-dlp-scan<br/>memory-link-rewriter<br/>memory-audit-log]
+    Tools -->|fail PR on violation| GH[GitHub Actions]
+    Folder -->|append-only| ChainLog[(.memforge-audit-log.jsonl<br/>tamper-evident chain)]
+```
+
+Adapters are thin: they translate "load this folder at session start" into the agent's native rules surface. Adding an agent means writing a new adapter, not changing the format.
+
+## Key tools
+
+Run `--help` on any of them.
+
+| Tool | What it does |
+|---|---|
+| `memory-audit` | Schema + integrity check. Pass `--strict` in CI. |
+| `memory-audit-deep` | Recursive audit: UID uniqueness, taxonomy membership, supersedes resolution, link integrity. |
+| `memory-index-gen` | Build `MEMORY.md` from frontmatter as a CI artifact. RBAC-aware filtering for shared folders. |
+| `memory-cluster-suggest` | Suggest rollup subfolders when a topic accumulates five or more memories. |
+| `memory-dlp-scan` | Pre-commit scanner for secrets, credentials, and PII in memory bodies. |
+| `memory-link-rewriter` | UID-based cross-folder link integrity (`check`, `rename`, `rename-batch`, `upgrade`). |
+| `memory-audit-log` | Append-only tamper-evident hash chain. JSONL on disk, exports CEF for SIEM. |
+| `memory-dedup` | LLM-backed near-duplicate detection. Local-only by default; reports candidates, never writes. |
+| `memory-rollup` | Bulk-move primitive: create / undo / list. Maintains an undo ledger. |
+| `memory-query` | Filter memories by topic, type, tag, status, owner, date range, or text. |
+| `memory-watch` | Filesystem watcher (Linux + macOS via watchdog). |
+| `memory-promote` | Move a memory between folders with index fixup. |
+
+The `tools/README.md` has the long-form reference.
+
+## Spec
+
+Format invariants are in [`spec/SPEC.md`](./spec/SPEC.md). Topic taxonomy is in [`spec/taxonomy.yaml`](./spec/taxonomy.yaml). The current package version is in `pyproject.toml`; the on-disk format version is in [`spec/VERSION`](./spec/VERSION). They track separately on purpose: a tooling release does not always shift the format, and a format bump is a deliberate event.
+
+## Status
+
+| Version | Date | Headline |
+|---|---|---|
+| v0.1.0 | 2026-04-19 | First spec release. |
+| v0.2.0 |  | Sensitivity classification (4 levels) + consumer obligations. |
+| v0.3.0 | 2026-05-07 | Schema expansion (uid, tier, tags, owner, last_reviewed, status), rollup-with-subfolder formalization, access labels, controlled topic taxonomy, full Phase 1 tooling, audit log, DLP scan. |
+| v0.4.0 | planned | Make `uid`, `tier`, `tags`, `owner`, `status`, `created` required (breaking). |
+
+The reference implementation is running in production. External adoption is welcome once the CLA flow is live.
+
+## License
+
+Apache-2.0. See [`LICENSE`](./LICENSE).
+
+The "MemForge" name and logo are subject to pending trademark filings; the Apache-2.0 grant does not cover the marks. A trademark policy will land alongside the v0.3.x CLA release.
+
+## Contributing
+
+External pull requests are paused. Issues and Discussions are open. See [CONTRIBUTING.md](./CONTRIBUTING.md) for the current model and the post-CLA contributor flow.

ildan_memforge-0.3.1/README.md

@@ -0,0 +1,155 @@
+# MemForge
+
+**Typed, git-native, dynamic memory for coding agents.** A markdown folder + a small spec + reference tooling. Works across Claude Code, Cursor, Aider, Codex, and GitHub Copilot Chat through thin adapters.
+
+> **Status: pre-1.0; external PRs paused.** Issues and Discussions are open. External pull requests are paused until the Contributor License Agreement infrastructure lands; the CLA flow will land in a v0.3.x patch release. See [CONTRIBUTING.md](./CONTRIBUTING.md). Security reports go through the private channel in [SECURITY.md](./SECURITY.md).
+
+## The gap MemForge fills
+
+Coding agents have static instruction surfaces (AGENTS.md, `.cursorrules`, `CONVENTIONS.md`, `.github/copilot-instructions.md`, Claude Code's auto-memory) for things you want the agent to read at the start of every session. They handle the "always-true" half well.
+
+What they don't handle: the **changing** half. The fact that you decided to use `bun` not `npm` last Tuesday. The reason you rejected the obvious database schema. The post-incident rule about not mocking the staging API. The seven things you've told four different agents the same way and are tired of repeating.
+
+That state belongs in *memory*: typed entries that the agent can read, write, audit, and version-control alongside the code. MemForge is the format for that memory and a small set of tools that keep it healthy.
+
+## What you get
+
+- **A folder of markdown files** with YAML frontmatter. Hand-editable, diffable, code-reviewable.
+- **Four memory types:** `user` (facts about the developer), `feedback` (rules they have given), `project` (state about ongoing work), `reference` (pointers to external systems).
+- **A `MEMORY.md` index** any agent loads at session start.
+- **Rollup subfolders** for topic clusters of five or more memories, so the index stays scannable.
+- **Audit + integrity tooling** that runs in CI: schema checks, link integrity, DLP scan, tamper-evident audit log.
+- **Adapters** for Claude Code, Cursor, Aider, OpenAI Codex, and GitHub Copilot Chat (VS Code).
+
+## 60-second install
+
+```bash
+pip install memforge   # publish target; not yet on PyPI as of v0.3.0
+# Or, until then:
+pip install git+https://github.com/ildan-ai/memforge.git
+```
+
+Pick a folder for your memory. The defaults the tooling assumes:
+
+```
+~/.claude/global-memory/                          # cross-project rules
+~/.claude/projects/<USER>-claude-projects/memory/ # per-cwd state
+```
+
+Other layouts work too; the tooling takes a `--path` argument everywhere.
+
+## A memory file, end-to-end
+
+```markdown
+---
+name: Use bun, not npm
+description: Bun is the package manager for this monorepo
+type: feedback
+tags: [topic:tooling, topic:javascript]
+status: active
+created: 2026-04-12
+---
+
+When installing or running scripts in this repo, use `bun` and `bunx`. Lockfile is `bun.lockb`.
+
+**Why:** the workspace setup at `apps/web/package.json` relies on bun's workspace resolver; npm pulls a slightly different dependency tree and the build fails downstream.
+
+**How to apply:** any time you reach for `npm install`, `npx`, or a `package-lock.json`, stop and use bun instead. If a script in the README still says `npm run`, treat that as a docs bug, not a directive.
+```
+
+That file is the unit. Every tool, every adapter, every check operates on files of exactly this shape.
+
+## When MemForge is the right tool
+
+- You move between coding agents and want them to share the same notes.
+- You want memory entries reviewable in pull requests, like code.
+- You want the operator to *see* what the agent has written about them and edit it freely.
+- You want CI gates on memory hygiene (broken links, secret leakage, schema drift).
+
+## When it is not
+
+- **Not a vector database.** No embeddings, no similarity search at runtime. Use `mem0` or `letta` if that is the shape you need.
+- **Not a secrets store.** The DLP scanner refuses files that look like they leak credentials, but the format is human-readable plain text. Keep secrets in a vault.
+- **Not a runtime memory layer.** MemForge is the *file format and the discipline*, not a service. Adapters load files into agent context at session start; nothing runs continuously.
+- **Not a replacement for AGENTS.md.** AGENTS.md is the README for agents (static, repo-level, project setup). MemForge is the working notebook (dynamic, evolving, often per-developer). They coexist.
+
+## How it compares
+
+| | **MemForge** | mem0 | letta | `.cursorrules` / `AGENTS.md` |
+|---|---|---|---|---|
+| Storage | Markdown files in git | Hosted vector store | Hosted agent state | Single text file |
+| Typed entries | Yes (4 types + status) | No | Partial | No |
+| Cross-agent | Yes (adapters) | Per-SDK | Per-SDK | Per-agent |
+| Reviewable in PRs | Yes (diff = the file) | No (opaque store) | No | Yes |
+| Runtime cost | Zero (load at session start) | Per-query embedding cost | Per-query | Zero |
+| Best for | Long-lived rules + decisions | Conversational recall | Stateful agent loops | Project-level setup |
+
+The honest summary: if your agent is a long-running service that needs to remember a thousand things from yesterday's chat, you want a vector store. If your agent is a coding session that needs to remember the rules and decisions a human cares about across sessions, you want MemForge.
+
+## Architecture
+
+```mermaid
+flowchart LR
+    Dev[Developer] -->|edits| Folder[Memory folder<br/>markdown + YAML]
+    Folder -->|read at session start| AdapterCC[Claude Code adapter]
+    Folder -->|read at session start| AdapterCursor[Cursor adapter]
+    Folder -->|read at session start| AdapterAider[Aider adapter]
+    Folder -->|read at session start| AdapterCodex[Codex adapter]
+    Folder -->|read at session start| AdapterCopilot[Copilot Chat adapter]
+    AdapterCC --> Agent1[Claude Code]
+    AdapterCursor --> Agent2[Cursor]
+    AdapterAider --> Agent3[Aider]
+    AdapterCodex --> Agent4[OpenAI Codex]
+    AdapterCopilot --> Agent5[GitHub Copilot Chat]
+    Folder -->|CI gate| Tools[memory-audit<br/>memory-dlp-scan<br/>memory-link-rewriter<br/>memory-audit-log]
+    Tools -->|fail PR on violation| GH[GitHub Actions]
+    Folder -->|append-only| ChainLog[(.memforge-audit-log.jsonl<br/>tamper-evident chain)]
+```
+
+Adapters are thin: they translate "load this folder at session start" into the agent's native rules surface. Adding an agent means writing a new adapter, not changing the format.
+
+## Key tools
+
+Run `--help` on any of them.
+
+| Tool | What it does |
+|---|---|
+| `memory-audit` | Schema + integrity check. Pass `--strict` in CI. |
+| `memory-audit-deep` | Recursive audit: UID uniqueness, taxonomy membership, supersedes resolution, link integrity. |
+| `memory-index-gen` | Build `MEMORY.md` from frontmatter as a CI artifact. RBAC-aware filtering for shared folders. |
+| `memory-cluster-suggest` | Suggest rollup subfolders when a topic accumulates five or more memories. |
+| `memory-dlp-scan` | Pre-commit scanner for secrets, credentials, and PII in memory bodies. |
+| `memory-link-rewriter` | UID-based cross-folder link integrity (`check`, `rename`, `rename-batch`, `upgrade`). |
+| `memory-audit-log` | Append-only tamper-evident hash chain. JSONL on disk, exports CEF for SIEM. |
+| `memory-dedup` | LLM-backed near-duplicate detection. Local-only by default; reports candidates, never writes. |
+| `memory-rollup` | Bulk-move primitive: create / undo / list. Maintains an undo ledger. |
+| `memory-query` | Filter memories by topic, type, tag, status, owner, date range, or text. |
+| `memory-watch` | Filesystem watcher (Linux + macOS via watchdog). |
+| `memory-promote` | Move a memory between folders with index fixup. |
+
+The `tools/README.md` has the long-form reference.
+
+## Spec
+
+Format invariants are in [`spec/SPEC.md`](./spec/SPEC.md). Topic taxonomy is in [`spec/taxonomy.yaml`](./spec/taxonomy.yaml). The current package version is in `pyproject.toml`; the on-disk format version is in [`spec/VERSION`](./spec/VERSION). They track separately on purpose: a tooling release does not always shift the format, and a format bump is a deliberate event.
+
+## Status
+
+| Version | Date | Headline |
+|---|---|---|
+| v0.1.0 | 2026-04-19 | First spec release. |
+| v0.2.0 |  | Sensitivity classification (4 levels) + consumer obligations. |
+| v0.3.0 | 2026-05-07 | Schema expansion (uid, tier, tags, owner, last_reviewed, status), rollup-with-subfolder formalization, access labels, controlled topic taxonomy, full Phase 1 tooling, audit log, DLP scan. |
+| v0.4.0 | planned | Make `uid`, `tier`, `tags`, `owner`, `status`, `created` required (breaking). |
+
+The reference implementation is running in production. External adoption is welcome once the CLA flow is live.
+
+## License
+
+Apache-2.0. See [`LICENSE`](./LICENSE).
+
+The "MemForge" name and logo are subject to pending trademark filings; the Apache-2.0 grant does not cover the marks. A trademark policy will land alongside the v0.3.x CLA release.
+
+## Contributing
+
+External pull requests are paused. Issues and Discussions are open. See [CONTRIBUTING.md](./CONTRIBUTING.md) for the current model and the post-CLA contributor flow.

ildan_memforge-0.3.1/pyproject.toml

@@ -0,0 +1,54 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "ildan-memforge"
+version = "0.3.1"
+description = "MemForge: portable, agent-neutral persistent memory for coding agents (ILDAN)."
+readme = "README.md"
+license = { text = "Apache-2.0" }
+authors = [
+    { name = "ILDAN" },
+]
+requires-python = ">=3.10"
+dependencies = [
+    "PyYAML>=6.0",
+    "watchdog>=4.0",
+]
+
+[project.optional-dependencies]
+dlp = [
+    "detect-secrets>=1.5",
+]
+dev = [
+    "pytest>=8",
+    "pip-audit>=2.7",
+]
+
+[project.urls]
+Homepage = "https://github.com/ildan-ai/memforge"
+Issues = "https://github.com/ildan-ai/memforge/issues"
+
+[project.scripts]
+memory-audit = "memforge.cli.audit:main"
+memory-audit-deep = "memforge.cli.audit_deep:main"
+memory-promote = "memforge.cli.promote:main"
+memory-audit-log = "memforge.cli.audit_log:main"
+memory-cluster-suggest = "memforge.cli.cluster_suggest:main"
+memory-dedup = "memforge.cli.dedup:main"
+memory-dlp-scan = "memforge.cli.dlp_scan:main"
+memory-frontmatter-backfill = "memforge.cli.frontmatter_backfill:main"
+memory-index-gen = "memforge.cli.index_gen:main"
+memory-link-rewriter = "memforge.cli.link_rewriter:main"
+memory-preamble-extract = "memforge.cli.preamble_extract:main"
+memory-query = "memforge.cli.query:main"
+memory-rollup = "memforge.cli.rollup:main"
+memory-watch = "memforge.cli.watch:main"
+agents-md-gen = "memforge.cli.agents_md_gen:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+memforge = ["py.typed"]

ildan_memforge-0.3.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+