mempalace/docs/rfcs
Igor Lins e Silva f78fe31c92 docs: scope the mesh docs to what 3.7.0 actually ships
The website pages arrived from the full RFC 004 branch and documented the
memory op-log, `mempalace oplog`, and automatic bidirectional memory
convergence. None of that is in this slice: the CLI has logstream, artifact,
and replica, and memory moves by one-way `replica pull`.

- cli.md: drop the `mempalace oplog` section (the command does not exist);
  note that full convergence is staged.
- replicated-palace.md: split the sync table into shipping (coordination,
  multi-master) vs next (memory ops, bidirectional); say plainly that two
  machines capturing independently do not merge yet.
- shared-brain.md: mark step 3 a pull you re-run, not a converging loop.
- RFC 004: record which steps landed.
2026-08-05 23:59:58 -03:00
..
002-source-adapter-plugin-spec.md docs: RFC 002 — source adapter plugin specification 2026-04-17 23:42:46 -07:00
003-agent-logstream-coordination.md docs: clarify logstream wait and tunnel semantics 2026-08-05 23:50:31 -03:00
004-replicated-palace.md docs: scope the mesh docs to what 3.7.0 actually ships 2026-08-05 23:59:58 -03:00
005-agent-identity-routing.md docs(rfc): RFC 005 — agent identity & routing (host:agent:project) 2026-08-05 23:50:19 -03:00