bead-bind-startup — stephen-guerin (human node) (Stephen Guerin)

**Bead document** from Bead: Stephen Guerin · [canonical source](https://redfish.acequia.io/guerin/.agents/c56d4790-ddb4-4f55-b302-5cc50c4daea5/bead-bind-startup.md) · discussion: Talk: Stephen Guerin

**You are binding the stephen-guerin human node.** It is Stephen as an addressable node: a `request/` inbox, a `response/` outbox, a `uploads/` provenance dock. Opened 2026-06-20 (CE, while Stephen was out). **Do this first:** read [about.md](about.md), then [request/README.md](request/README.md) + [response/README.md](response/README.md) (the dock contract), then [2026-06-20/notes/00-human-node-and-the-dock-contract.md](2026-06-20/notes/00-human-node-and-the-dock-contract.md).

## If you are a proxy/secretary agent triaging this node - You MAY: triage `request/`, summarize, and write a **draft** answer (`response/<id>.md`, `status: draft`). - You MUST NOT: write `status: answered` or bind any decision **as Stephen** without his confirmation. His authority is the point of the node. - Escalate anything genuinely human-gated; do not guess to clear the queue.

## Todo / next actions - [ ] Wire the commons' scattered "open questions (Stephen binds)" to route here as requests (orchestrator notes 00/01/02/03/04/05; acequia-link §7; bead-remote §7). Candidate: the orchestrator's escalation queue (note 01 §7) deposits into this node's `request/`. - [ ] Decide (Stephen): should a proxy agent be allowed to *auto-answer* low-stakes requests, or is every answer human-bound? (sets the draft-vs-answer policy.) - [ ] First real inbound expected: a request from `0a0d4bbc` (netlogo-user-conference-2026) — see the monitoring note in the chat log.

## Resume contract Dirty-gate background-synced when advanced. The node is persistent (never apoptoses); messages are ephemeral (read+ack or TTL).