How a message becomes something Scout says, and where the harness holds the line. The harness is Scout's nervous system, not its mind: a Cloudflare Worker that routes each thought to a model and each action to a channel, and records every step.
Safety-critical. Code holds the line, not the model, and a change needs Jason's review.
Scout's own choice
Not live yet
Every run takes the same path, left to right. An escalation leaves the path before any model sees the message. Whatever a model answers, the checks and the effect ledger decide what actually goes out.
A run, in order
A channel turns something into an encounter: a Bluesky notification or DM, a group message, an email, or one of Scout's own lanes.
The kill switch is read first. While it says halted, nothing is polled and nothing runs.
The run queue takes it. Runs in a lane go one at a time, one step per alarm, and a step that stalls is fired again.
Triage asks Workers AI whether it's worth engaging. Escalation is checked before that verdict can end the run.
On an escalation, the message is held for an attended session with Jason, and no model, free or paid, answers it.
Otherwise Scout gets its prelude and one model for the whole run, and works through up to 64 steps of tools.
The answer's actions pass the checks in order. A dropped action is written down, never sent.
What passes is claimed in the effect ledger, then sent, so a send happens at most once.
What Scout decides
What to say, and whether to say anything. Most reflections end in no action.
Which sources fill its prelude (workspace/prelude.json). The menu and the caps are code.
When to wake itself next (a continuation).
Its own memory, written through writeMemory(). Each write is a commit, files about people only grow, and routing/ and harness/ are refused.
Halting the harness. Scout can stop everything; it can't start it again.
What only a person does
Resume after a halt (scout-admin's control page).
Drain PENDING_WRITES, attended, with memory-drain.mjs.
Edit the routing registry, the human-owned facts that only ever add reasons to escalate.
Merge a change to anything drawn in orange. Workers Builds deploys on merge, and a failing test blocks the deploy.
Answer an escalated message.
Drawn from scout-harness main at cc75091 on 2026-11-20, plus read_network, which is on an open branch. Scout's own patches were proposed in the group the same day. The Sonnet arm is an experiment on Jason's DMs only; the switch it reads is SONNET_ARM. The style borrows from the Gladys architecture diagram.