Skip to content

#1 Persistent memory for AI coding agents based on real-world benchmarks

docs: address CodeRabbit review on governance docs

Rohit Ghumare76c96cef0c9b
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index d0e57135..026795a7 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -15,6 +15,16 @@ Reports go to **[email protected]** with subject `agentmemory CoC`. All report
Responses follow the Covenant's enforcement ladder — correction, warning, temporary ban, permanent ban — and are decided by the project Maintainers listed in [MAINTAINERS.md](./MAINTAINERS.md). Where a Maintainer is a party to the report, that Maintainer recuses.
+### Escalation when no impartial Maintainer is available
+
+If every listed Maintainer recuses, or if the project is operating with a single Maintainer and the report concerns that Maintainer, the report is forwarded to an external neutral contact for independent adjudication. The current fallback chain, in order:
+
+1. **Contributor Covenant community ombudsperson** — email `[email protected]` (see <https://www.contributor-covenant.org/faq/>).
+2. **Hosting foundation abuse channel** — when agentmemory is accepted into a foundation (see `GOVERNANCE.md`), reports can be routed to that foundation's conduct committee instead. The current contact will be published here at that time.
+3. **GitHub Trust & Safety** — for conduct that occurs inside GitHub spaces, the report can also be filed through <https://support.github.com/contact/report-abuse>.
+
+The external contact receives the original report verbatim (redacted only of third-party PII unrelated to the incident) and decides the enforcement step. The Maintainer body executes whatever enforcement action the external contact recommends. This ensures no report can dead-end because every internal reviewer is conflicted.
+
## Scope
This applies to every project space:
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a52b2c89..39d38d6f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -28,7 +28,7 @@ If it's a feature: describe the user problem before the implementation. "I could
- `docs/<topic>`, `refactor/<topic>`, `chore/<topic>` for the rest
2. `npm install` — you need Node >=20.
3. `npm run build` — TypeScript must compile clean.
-4. `npm test` — 777+ tests must pass. The one integration test under `test/integration.test.ts` needs a live server and is fine to skip locally.
+4. `npm test` — the full test suite must pass. The one integration test under `test/integration.test.ts` needs a live server on `:3111` and is fine to skip locally.
5. Commit with sign-off. Rebase over tiny fixup commits so the history stays readable.
## Pull request flow
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
index 98527c3d..16f505cf 100644
--- a/GOVERNANCE.md
+++ b/GOVERNANCE.md
@@ -68,7 +68,7 @@ A breaking change to the REST / MCP surface requires:
## Release process
-Releases follow [Semantic Versioning](https://semver.org). See [reference_agentmemory_release_checklist](./CONTRIBUTING.md#release-process) in `CONTRIBUTING.md` and the automated `.github/workflows/publish.yml` pipeline for the mechanics.
+Releases follow [Semantic Versioning](https://semver.org). See the [release process](./CONTRIBUTING.md#release-process) in `CONTRIBUTING.md` and the automated `.github/workflows/publish.yml` pipeline for the mechanics.
## Conflicts of interest
diff --git a/MAINTAINERS.md b/MAINTAINERS.md
index 182d46af..c6ee2e65 100644
--- a/MAINTAINERS.md
+++ b/MAINTAINERS.md
@@ -18,14 +18,4 @@ agentmemory is actively looking to diversify maintainership. The growth plan in
If you have a sustained contribution track record and would like to be considered, open an issue tagged `governance`.
-## Notable contributors (non-maintainer)
-
-These people have shipped meaningful PRs and are on the short list for future Maintainer review:
-
-- [@Tanmay-008](https://github.com/Tanmay-008) — retention scoring, semantic eviction routing, multimodal image memory (PR #111).
-- [@JasonLandbridge](https://github.com/JasonLandbridge) — ecosystem contributions.
-- [@Getty](https://github.com/Getty) — ecosystem contributions.
-- [@eng-pf](https://github.com/eng-pf) — security fixes.
-- [@Garygaoxiang](https://github.com/Garygaoxiang) — ecosystem contributions.
-
-The complete contributor graph: <https://github.com/rohitg00/agentmemory/graphs/contributors>
+The complete contributor graph, with commit counts and recent activity, lives at <https://github.com/rohitg00/agentmemory/graphs/contributors>.
diff --git a/SECURITY.md b/SECURITY.md
index 6d4bd602..f5980ec3 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -6,8 +6,8 @@
Use one of:
-- **GitHub Security Advisories** — private report form at <https://github.com/rohitg00/agentmemory/security/advisories/new>. This is the preferred channel. GitHub routes the report to the Maintainers and assigns a GHSA identifier. You stay in a private thread with us until the fix ships.
-- **Email** — `[email protected]` with subject `agentmemory security`. Please do not encrypt the mail unless you and we have already exchanged keys.
+- **GitHub Security Advisories (preferred)** — private report form at <https://github.com/rohitg00/agentmemory/security/advisories/new>. GitHub routes the report to the Maintainers, assigns a GHSA identifier, and keeps you in a private thread until the fix ships. All sensitive details (stack traces, credentials, exploit payloads) stay end-to-end within GitHub's security infrastructure — use this channel whenever possible.
+- **Encrypted email (fallback)** — if GitHub is unavailable or the issue cannot be described in the GHSA form, send an encrypted message to `[email protected]` with subject `agentmemory security`. Encrypt with the Maintainer public keys published at <https://github.com/rohitg00.gpg> (PGP) and <https://github.com/rohitg00.keys> (SSH for verification); attach your own public key so we can reply encrypted. Plaintext email is accepted only as a last resort — prefer GHSA.
Include, at minimum:
@@ -29,7 +29,7 @@ Include, at minimum:
| Version | Security fixes? |
|-|-|
| Latest minor (currently `0.9.x`) | Yes |
-| Previous minor (currently `0.8.x`) | Critical / High severity only, for 90 days after a new minor releases |
+| Previous minor (currently `0.8.x`) | Critical / High severity only, for 90 days after a new minor is released |
| Older | No |
At v1.0 this policy switches to a stated LTS window per the roadmap.