chiefofstaff.io
Get the prompt
The vault 146 files

Demo / the vault

Tools/review-surface/README.md

The review surface

One page. It renders the disposition queue Hobbs writes beside a brief or a weekly review, and turns each ask into three answers: yes, no, or defer with a named trigger. ADR-29.

Run it

node Tools/review-surface/server.mjs      # http://127.0.0.1:7317
PORT=8080 node Tools/review-surface/server.mjs

Node 22, no dependencies, no build step, no login. It binds to 127.0.0.1 only: laptop, not phone. The phone loop belongs to the channel and is still gated on the Pike decision.

What it reads

Efforts/dispositions/<date>-<kind>.json — the queue, written by Hobbs. Efforts/dispositions/<date>-<kind>.answers.jsonl — append-only. Last line wins, so a changed mind is a second line and never an erased one.

What a click does

  1. Appends one line to the answers file, with provenance: by: Rowan, via: review-surface, the source document, and the ask id.
  2. Runs the mechanical effects the queue file declared for that answer — close, priority, label, note, and hobbs (a declared hand-off, which writes nothing to the graph). Anything else is refused, loudly, and the answer is still recorded. Task-graph writes are attributed to --actor=Rowan.
  3. Writes an intention file to Efforts/inbox/ if the answer carries his words or a hand-off. Hobbs executes it with context on the next triage, and writes the curation-log line and the brief line — ADR-03 rails 3 and 4 are his, not the tool’s.
  4. Makes one git commit, prefixed rowan: rather than cos:, because the decision is his and the log should not be able to confuse the two.

The boundary

The tool has no judgment, so none is asked of it. Every effect was written by Hobbs into the queue file, with the vault in front of him, at the moment the ask was written. Rowan supplies the choice; the app supplies neither.

It never writes prose into Atlas/. It never invents an ask. It cannot reach anything outside this repository.

Undo

Every action is one commit. git revert <sha> is the undo, and re-answering an ask appends a new line rather than editing the old one.

Markdown source 
# The review surface

One page. It renders the disposition queue Hobbs writes beside a brief or a
weekly review, and turns each ask into three answers: yes, no, or defer with a
named trigger. **ADR-29.**

## Run it

```bash
node Tools/review-surface/server.mjs      # http://127.0.0.1:7317
PORT=8080 node Tools/review-surface/server.mjs
```

Node 22, no dependencies, no build step, no login. It binds to `127.0.0.1` only:
laptop, not phone. The phone loop belongs to the channel and is still gated on
the Pike decision.

## What it reads

`Efforts/dispositions/<date>-<kind>.json` — the queue, written by Hobbs.
`Efforts/dispositions/<date>-<kind>.answers.jsonl` — append-only. Last line wins,
so a changed mind is a second line and never an erased one.

## What a click does

1. Appends one line to the answers file, with provenance: `by: Rowan`,
   `via: review-surface`, the source document, and the ask id.
2. Runs the mechanical effects the queue file declared **for that answer** —
   `close`, `priority`, `label`, `note`, and `hobbs` (a declared hand-off, which
   writes nothing to the graph). Anything else is refused, loudly, and the answer
   is still recorded. Task-graph writes are attributed to `--actor=Rowan`.
3. Writes an intention file to `Efforts/inbox/` if the answer carries his words
   or a hand-off. Hobbs executes it with context on the next triage, and writes
   the curation-log line and the brief line — ADR-03 rails 3 and 4 are his, not
   the tool's.
4. Makes one git commit, prefixed **`rowan:`** rather than `cos:`, because the
   decision is his and the log should not be able to confuse the two.

## The boundary

**The tool has no judgment, so none is asked of it.** Every effect was written by
Hobbs into the queue file, with the vault in front of him, at the moment the ask
was written. Rowan supplies the choice; the app supplies neither.

It never writes prose into `Atlas/`. It never invents an ask. It cannot reach
anything outside this repository.

## Undo

Every action is one commit. `git revert <sha>` is the undo, and re-answering an
ask appends a new line rather than editing the old one.