Doc sets (the owner's document review page)
A doc set holds one piece of work's documents. When an agent proposes a new vision or strategy, you get one card in your inbox; one tap opens a page that shows exactly what changes and the whole new text, and Approve or Decline lands it. You can read and decide it on your phone, and no agent or script can approve on your behalf.
On this page
What it is
A doc set is the document home for one piece of work:
- Vision — the outcome, in bullets. Owner-approved.
- Strategy — the bet, in the approved five-part shape. Optional, owner-approved.
- Rules — the standing rules for the work. Read first; edited without approval.
- Records — short decision and lesson notes, added and never rewritten (a change is a new record that supersedes the old).
The documents live in the app database, not in a folder or a Git repository. Everything is bullets with nested bullets where they help, so it reads fast on a phone.
Where to find it
The alert is the front door. A proposal filed on a doc set you approve raises one card in your inbox, titled like “Checkout rewrite: approve the new vision?”. The card has one button — Review and approve — and that button opens the page.
The page is a full-screen Document review view, built phone-first:
- the doc set's title and the proposal's why;
- What changes — removed lines struck, added lines marked, unchanged lines faded for context, each wrapping on a narrow screen and indented where the bullet is nested;
- The whole new text, rendered as real bullets and nested bullets;
- The other documents of the doc set, each one tap to read;
- Who approves this doc set — you, in the app, or the group's lead;
- an optional Reply box, then Approve and Decline.
While the proposal is open the footer offers Approve and Decline. Once it has been decided the page shows the outcome, when it was decided, who decided and your reply, with no decision buttons — so an old link or a second look can never act twice.
How it behaves
One card per proposal, and it takes itself away
A card is keyed to the exact proposal it announces, so approving one proposal never closes a different one. It disappears when the proposal is approved, declined, or replaced by a newer revision — and when you switch the doc set to the group's lead.
The decision is compare-and-swap
The proposal remembers the revision of the document it was written against. Approving it appends the next revision, and any other open proposal for the same document built on an older revision is marked replaced (its card closes too). If the document moved since the proposal was written, the approval is refused with a plain sentence and nothing changes; the page says so.
If you put the card away by accident
Archiving the card does not withdraw the proposal — it stays open, waiting. The card is not lost: open the inbox's Recently dismissed and restore it. There is no timer that re-raises it for you.
Your reply travels with the decision
Whatever you type in Reply is stored with the decision and sent to the group's current lead in one message, together with where to read the new text.
Who decides: you, or the group's lead
Every new doc set is approved by you, in the app. On the review page you can switch a doc set to the group's lead. Then that lead decides through the agent-facing delegate command, and you get no cards for it. Switching back to you raises a card for anything already waiting.
Agents can read, but never decide
An agent reads a doc set through the CLI control server, and a member session proposes a change with a plain-words why. There is deliberately no control-server command that approves or declines as the owner: the install-wide CLI key is readable by any local process, so a route behind it could not prove it was you. The decision exists only in the app — on the desktop or a paired phone through Mobile Access.
Last verified 2026-11-11