Chapter 12 · agent-neuron · Lab
A team decides
Three invented people decide which of two agent patches lands, on real git: votes by quorum, the merge by a lead, the ledger on every page.
The decision surface
Two agent contributions sit on real branches of a scratch git repo, and the candidate ask lands as two desk items, one for each reviewer. Their votes join through a threshold-2 tally; the direction answers "settled by quorum" or "tie", and the same answer is the gate item the lead sees: one Merge button, or both branches and Refuse. The merge is apply, declared an effect: a real git commit with its tag. A budget of 12 credits puts a reserve and a commit per call in the trace.
Each person has a page (/p/ada, /p/lin, /p/sam) filtered to their own items, and one shared ledger (/log) carries every vote, accept and refusal with who and when; the names live in the ledger and in no protocol body. Two headless paths answer through the same POST the page uses, one to a quorum and one to a tie.
The rule it proves
The same rules the storm runs alone run a decision: a human neuron is an item on a desk (SPEC 3.4, decision 0008), the quorum is a plain threshold (5.2), the merge is an effect nothing cuts (11), and the credits are the budgets of 10. The graph is the referee; nobody built a controller for the team.
Run it
npm run demo:team # browsers: three pages and one merge
npm run demo:team -- --headless # the whole flow, no browsers
npm run demo:team -- --headless --tie # the tie: the lead refuses, nothing mergesWhat it is not
Not a product: the people, the module and the repo are invented and rebuilt on each run, the ledger is the demo proxy’s rather than the engine’s, and the holds that would let an answer wait out a restart are issue #30’s.