Chapter 10 · agent-neuron · Lab
A person in the loop
A person approves, edits or refuses proposed rewrites on a local page, and the run ends when every note is answered.
The desk, decision 0008
Three invented release notes go to a neuron that proposes a tighter wording, then to editor: a human neuron. The engine opens a page on 127.0.0.1 and prints its address; each note is an item that shows the draft beside a word diff of the proposal, answered with Approve, Edit or No. Publish, which is declared an effect, answers with what was approved, and the run ends when every note is.
The rule it proves
A person is a neuron kind (SPEC 3.4, decision 0008): the wrapper asks, the person answers through the desk page the engine serves (Appendix D), and the reply rides the same one-JSON-value contract. A newer note for the same item would withdraw the waiting one, and the thing publish does is an effect (11), so an approval that was sent cannot be unsent.
Run it
npm run demo:humanWhat it is not
Not a wait that survives anything: a restart loses the page and the waiting questions, one page carries one run, and who may answer is this demo’s own pairing, with the grants that pin it built later (issue #30).