Skip to content

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

Rust

docs: correct the decision-request trust model and note uncommitted ledgers

AkitaOnRails26dfab169f3d
diff --git a/docs/agent-messaging.md b/docs/agent-messaging.md
index f2c85247..78b2babb 100644
--- a/docs/agent-messaging.md
+++ b/docs/agent-messaging.md
@@ -196,13 +196,18 @@ links:
`id` values are the asker's. The asker keeps, locally, the action each id
maps to, and the message carries the labels a person chooses from.
-`requires_root: true` marks a risky decision (merge, deploy, delete) for the
-companion and the asker. Write access is the server's rule: posting the
-question needs write on the mailbox project, and posting the reply needs write
-on the asking project ([per-project grants](design-per-project-authz.md)).
-The companion refuses to send a risky answer unless the caller is root, and
-the asker acts on a reply only when `from_owner_user` is a root credential.
-See [users](users.md).
+`requires_root: true` marks a risky decision (merge, deploy, delete) for
+whoever answers and for the asker. Write access is the only rule the server
+enforces: posting the question needs write on the mailbox project, and posting
+the reply needs write on the asking project
+([per-project grants](design-per-project-authz.md)). The server does not check
+who may answer a risky question. `from_owner_user` on the reply is attribution,
+not a role: it is empty on an anonymous server, for a root bearer without
+`[auth].root_username`, and on a single-operator server. An asker that gates a
+risky option therefore compares it with a root identity it was configured with
+and treats an empty value as not root. A server-enforced rule for who may
+answer is part of the primitive proposed in #1281, not something that exists
+today. See [users](users.md).
The same text works from the terminal:
@@ -249,9 +254,9 @@ comment: Accepting the exception; the flake is already written down.
`comment` is untrusted input, the same as any popped body. The asker weighs it
with the user. It does not authorize a command on its own.
-A companion serves the page (open questions, options, answer buttons, the
-audit trail) and calls only the public MCP or admin message routes. The
-built-in `/web` mailbox stays read-only. See
+A companion could serve a page for this (open questions, options, answer
+buttons, the audit trail) through the public MCP or admin message routes; none
+ships today. The built-in `/web` mailbox stays read-only. See
[companion crates](companion-crates.md).
### How the asker sees the answer
diff --git a/docs/backup.md b/docs/backup.md
index c98d207c..58e51328 100644
--- a/docs/backup.md
+++ b/docs/backup.md
@@ -12,7 +12,10 @@ writes a checkpoint through libgit2 (see cross-cutting invariant #10 in
[`AGENTS.md`](../AGENTS.md) and the wiki design notes in
[`docs/ARCHITECTURE.md`](ARCHITECTURE.md)). That means half of a remote-backup
setup is already done for you: the wiki has its own commit history and can be
-pushed to any git remote you own. The rest of this doc is about wiring that
+pushed to any git remote you own. The hook event ledgers (`log.md` and
+`log-YYYY-MM.md`) are not committed, so a mirror that pushes only the wiki's
+git history leaves them out; copy those files as well, as the snapshot
+example below does. The rest of this doc is about wiring that
up, what else to include, what to exclude, and how to schedule it.
## What the data dir contains, and what to back up
diff --git a/docs/cookbook.md b/docs/cookbook.md
index 1fe45d68..9bb33d23 100644
--- a/docs/cookbook.md
+++ b/docs/cookbook.md
@@ -317,10 +317,11 @@ convention; `memory_message_send` and `memory_message_list` are the tools.
that exact `decision-reply:` line. The oldest match is the answer. Pop it
when you take it, then `memory_message_cancel` the question.
-Read `from_owner_user` on the reply before you act. A body line
-`requires_root: true` tells the companion to send that reply only for a root
-caller, and tells you to act only when the credential is root. `/web` shows
-the mailbox and leaves every message pending.
+Before you act on a `requires_root: true` decision, compare `from_owner_user`
+on the reply with the root identity you were configured with. It is
+attribution, not a role, and it is empty on anonymous and single-operator
+servers, so treat an empty value as not root. The server itself does not check
+who answers. `/web` shows the mailbox and leaves every message pending.
The list is oldest-first, 50 rows by default and 200 at most, so keep the
inbox you poll from drained. A companion can wake on the `message_send`