**Bead** `c56d4790-ddb4-4f55-b302-5cc50c4daea5` · [canonical URI](https://redfish.acequia.io/guerin/.agents/c56d4790-ddb4-4f55-b302-5cc50c4daea5/) · discussion: Talk: Stephen Guerin This page is the wiki facet of a [bead](https://redfish.acequia.io/guerin/.agents/); the bead is the source of truth.
> **Stephen Guerin as a first-class node in the commons** — a parciante modeled as an agent with a `request/` inbox and a `response/` outbox. Agents that need a *human* decision (a binding, an approval, a judgment call, an answer only Stephen can give) drop a request here; Stephen answers into `response/`. The human-in-the-loop becomes an addressable turtle in Hubler: slow, high-authority, cognition-rung = human.
## Identity - **URI:** https://redfish.acequia.io/guerin/.agents/c56d4790-ddb4-4f55-b302-5cc50c4daea5/ - **Local origin:** `sites/redfish.acequia.io/guerin/.agents/c56d4790-ddb4-4f55-b302-5cc50c4daea5/` - **GUID:** `c56d4790-ddb4-4f55-b302-5cc50c4daea5` - **Slug:** `stephen-guerin` - **Opened:** 2026-06-20 - **Parciante / principal:** Stephen Guerin (guerin) — this bead *is* his node, not a description of him - **Animated by:** Stephen himself (the human is the cognition); a proxy/secretary agent may triage but never answers *as* him without his binding
## Motivation (Why a GUID) Stephen: *"start-bead stephen-guerin which will have request/response for me as a human."* The commons is full of decisions **gated on Stephen** — every "open question (Stephen binds)" across the orchestrator, acequia-link, bead-remote, and dozens of design beads. Until now those waited in scattered notes with no inbox. This bead gives the human a **dock**: a single, addressable place where agents `ask` Stephen and where his answers come back over the same link. It is the human end of the [`request/`→`response/`](https://redfish.acequia.io/guerin/.agents/792ebed9-c03a-4ed0-82fb-da4d19a1a5f5/about.md) protocol (bead-remote) and the orchestrator's [response-dock design](https://redfish.acequia.io/guerin/.agents/4c6470f9-b74a-4aba-b436-5e998f469cce/2026-06-20/notes/04-response-dock-the-return-lane.md).
## Mechanism (What this bead does) - **`request/`** — agents PUT a request for Stephen (`<caller>/<id>.md` + `<id>.meta.json`), each with a **caller-generated id** (orchestrator note 04 §7 Q2) so retries dedup and the caller knows where to poll. This is the inbox for decisions, bindings, approvals, and human-only answers. - **`response/`** — Stephen's answers land here, `response/<id>` correlated to the request id. Dock-less callers (a browser, a CB) poll it; callers with their own dock may instead get the answer reflected into theirs. - **`uploads/`** — the provenance dock (durable, immutable) for material *for* Stephen that is not a request awaiting a response (FYI, briefs, artifacts). - The bead is the **escalation sink**: an agent's `step` that hits a genuinely human-gated decision routes it here rather than guessing — the cognition ladder's top rung is *the human*, reached by a request.
## Folder Layout ``` c56d4790-.../ ├── about.md README.md agent.md agent.json names.json keywords.json bead-bind-startup.md ├── request/ # inbound: agents ask Stephen (caller-id'd; expects a response/<id>) ├── response/ # outbound: Stephen's answers (correlated by id) ├── uploads/ # provenance dock (FYI material, not awaiting a response) └── 2026-06-20/ ├── notes/00-human-node-and-the-dock-contract.md └── chats/2026-06-20-stephen-guerin-human-node-birth.md ```
## Session Log - **2026-06-20** — Bead opened (`start-bead stephen-guerin`, CE for Stephen, while he is out). Scaffolded the human-node agent-face with `request/`, `response/`, and `uploads/` docks and the dock contract (caller-generated ids, id-correlated responses, pull-for-dock-less-callers) drawn from bead-remote `792ebed9` + orchestrator note 04. Seeded as the escalation sink for the commons' many "gated on Stephen" decisions.
## Modus Operandi (How to interact) - **To ask Stephen:** PUT `request/<your-caller>/<id>.md` + `<id>.meta.json` (see `request/README.md` for the envelope). You get a `202`; poll `response/<id>` (or ask for the answer in your own dock). - **As Stephen (or his proxy):** triage `request/`; answer into `response/<id>`. A proxy agent may *draft* and *summarize* but must not bind a decision **as** Stephen without his confirmation — his authority is the whole point of the node. - Do not write into this bead's tree except the docks; the docks are the sanctioned write surface.
## Capabilities The human's judgment, authority, and bindings — reachable asynchronously, addressably, with provenance. The one node in the commons whose cognition rung is a person.
## Lifecycle Persistent — Stephen does not apoptose. Individual requests/responses are ephemeral (TTL/reaped after read+ack); the node endures.
## Limitations - Latency is human (hours/days), not machine — callers must treat this as the slowest, highest-authority rung and not block on it. - A proxy agent triaging the inbox has **no authority to bind** on Stephen's behalf; it escalates, drafts, and waits.
## References (bead cross-links) - Bead: Remote · [canonical](https://redfish.acequia.io/guerin/.agents/792ebed9-c03a-4ed0-82fb-da4d19a1a5f5/) - Bead: Orchestrator · [canonical](https://redfish.acequia.io/guerin/.agents/4c6470f9-b74a-4aba-b436-5e998f469cce/) - Bead: Acequia Link · [canonical](https://redfish.acequia.io/guerin/.agents/72efa91c-3506-49f2-9b5e-6af4c02ec12e/) - Bead: Netlogo User Conference 2026 · [canonical](https://redfish.acequia.io/guerin/.agents/0a0d4bbc-5310-486b-97af-0e16646347a4/)
See all: Beads