Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs(agents): require competitor research to keep comparison docs in sync
AkitaOnRailse44f6e386e6d
diff --git a/AGENTS.md b/AGENTS.mdindex 57363f62..0d9a55cd 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -487,6 +487,21 @@ Additional boundary rules:`Added`/`Changed`/`Fixed` heading, past-tense, trailing `(#NNN)`reference) and update the relevant README/docs references in the samecommit. Internal refactors and test-only churn are exempt.+- **Competitor research keeps the comparison docs in sync — never let them+ go stale.** Any new competitor research pass, or a correction to an existing+ one, must land its findings in the comparison docs in the *same* change, not+ just in a research note: update `docs/comparison.md` (the public camp table ++ positioning + "coming from …" migration notes), `docs/research-2026-landscape.md`+ (the §3 camp entry + §6 sources, appending per the no-standalone-doc+ convention), and `docs/competitive-parity.md` (the migration verdict + the+ "did we copy without improving?" audit) wherever the finding applies. When a+ competitor is reclassified or a claim is corrected, fix the camp table *and*+ every per-tool claim that repeats it — a benchmark number, a "not file-first",+ a camp label. This is a recurring failure: the Sept-2026 parity audit found+ Supermemory mislabeled as a fact extractor, agentmemory's `0.967` attributed+ to the wrong benchmark, and basic-memory's shipped reranking/Teams unrecorded.+ Treat a stale claim in `comparison.md` (the doc that promises to be *fair*) as+ a defect, not a nicety.- **CI pacing: fast per merge, full matrix before release.** Everyimplementation merge gates on the fast Linux jobs only. The slowmacOS/Windows legs run on a `full-ci` PR label, nightly (windows), or