Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

docs: record the web write surface as a non-goal, not a pending iteration

AkitaOnRails036ef88749e6
diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md
index 9a9fb102..660fa050 100644
--- a/docs/ARCHITECTURE.md
+++ b/docs/ARCHITECTURE.md
@@ -597,12 +597,13 @@ when `LLM_API_KEY` is absent and stores vectors under the distinct
* **Richer curator actions.** The shipped curator stages only one report page;
future work can add individual merge/supersession/link-fix proposals while
keeping deletes and semantic rewrites review-gated.
-* **Write surface for the web UI.** The multi-workspace read-only wiki
- browser shipped in `ai-memory-web` (`/web` — project list, page tree,
- page view, search). Browsers still can't mutate anything (notes,
- consolidate, lint, purge stay CLI/MCP-only); an authenticated "edit
- this page" surface is a deliberate v2 conversation. See
- [`docs/frontend-api.md`](frontend-api.md#10-known-gaps-planned-iterations-not-blockers).
+* **Richer read surfaces for the web UI.** The multi-workspace read-only
+ wiki browser shipped in `ai-memory-web` (`/web` — project list, page
+ tree, page view, search). It stays read-only by design: the wiki is a
+ machine-authored record, and a browser edit surface would break the
+ invariant the whole store rests on (#482). Better *reading* — richer
+ navigation, diff/history views, graph exploration — is open. See
+ [`docs/frontend-api.md`](frontend-api.md#10-known-gaps-and-deliberate-non-goals).
* **Real LongMemEval-S harness.** The recall-eval framework exists
([`crates/ai-memory-consolidate/tests/recall_eval.rs`](../crates/ai-memory-consolidate/tests/recall_eval.rs));
porting LongMemEval-S itself requires the dataset.
diff --git a/docs/frontend-api.md b/docs/frontend-api.md
index f55e7142..10e8d8c6 100644
--- a/docs/frontend-api.md
+++ b/docs/frontend-api.md
@@ -708,12 +708,23 @@ accepting wildcard. The layer allows `GET / POST / OPTIONS`,
`Authorization` + `Content-Type` headers, and credentials, with a
10-minute preflight cache.
-## 10. Known gaps (planned iterations, not blockers)
-
-- **Write surface.** Browsers can't mutate today (notes, consolidate,
- lint, purge — all live under `/admin/*` for the CLI or under MCP
- tools for agents). A thin authenticated write surface ("edit this
- page" from the browser) is a deliberate v2 conversation.
+## 10. Known gaps and deliberate non-goals
+
+- **No write surface, by design — not a pending iteration.** Browsers
+ can't mutate, and won't. The wiki is a record of what a project
+ produced, authored by automated summarisation over captured
+ observations; retrieval, provenance and the audit trail all rest on
+ nobody having gone back and adjusted it. Hand-editing a page stops it
+ answering "what did this project produce" and starts it answering
+ "what did someone want it to say", with no way to tell the two apart
+ afterwards.
+
+ This is not a ban on human input. `memory_write_page` exists for
+ durable human annotations and lands them in the same lineage as
+ everything else (pages supersede on body change). The line is between
+ adding to the record through the normal path and editing it from
+ outside. A human-editable wiki is a reasonable thing to want and a
+ separate product — see #482.
- **Rate limiting** is shared with `/mcp` + `/admin` (only the body
cap is enforced today). A future global limiter would tighten the
authenticated-misbehaviour case.