Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.
JavaScript agentic-codingai-agentsai-governanceautonomous-agentsclaude-codeclicode-reviewcodexcoding-agentsdeveloper-toolsgit-hooksllmlocal-firstmulti-agentsoftware-factoryspec-driven-developmentverificationvibe-coding
docs(person): describe exact signed row source [E22,H16]
Corey Olson70d6db17929d
diff --git a/docs/api.md b/docs/api.mdindex b32c4b9e..349eaf1b 100644--- a/docs/api.md+++ b/docs/api.md@@ -504,6 +504,8 @@ Every signed row and signer-list change binds the initial signer-list hash in itWith signing on, a person move from a terminal, SSH and remote shells included, is refused at once with `PERSON_SIGNED`, whatever the shell markers say. On an unlinked board, or one with no relay, the next step is to pair a phone or a computer browser with `pullboard relay on --all` and add a passkey there. On a linked board the terminal first records the exact move as a request for the person's passkey device (`proposePersonMove`), and the initiating terminal names the request and confirmation address, then waits while the existing native executor carries out the one confirmed action. Its successful JSON keeps the command's usual required fields and adds `request` and `status`; a repository-changing decision may also name its `coordinatorRequest`, which is not a landing receipt. No second terminal command is required. The local view's channel takes the same refusal: a file the user can read is no proof of the person. Turning signing off is refused from every terminal; only a passkey-confirmed request turns it off, and no edit to `pullboard.json`, machine settings or a board row does. `pullboard relay off` still unlinks offline with no tap and leaves signing on. A row whose source names `signers:` is refused with `PERSON_SIGNER_REQUIRED`, naming the row and its principals: a passkey stands in for an optional SSH sign-off but not for a named signer. With signing off, SSH sign-offs work as described below.+Signed spec/doctrine requests include `rows: [{id, text, source}]`: `source` is the complete original one-line row, including its gate and named signers. The passkey confirms that exact source together with the requested replacement or answer; missing or changed source fails closed. Approval projection and file application also require the exact committed row event and its matching request execution receipt. Mutable metadata, a copied stamp, or a locally inserted event cannot authorize a changed source row. These checks do not establish the separate first-authority trust anchor.+A passkey is any WebAuthn credential the person registered on the relay with user presence: a phone's Face ID or Touch ID, or a computer browser's. The relay page offers to add one while a paired board signs person moves, and shows each waiting terminal-started move with a Confirm button. The endpoints, all on the relay's configured origin:| Endpoint | Who | Body | Answer |diff --git a/test/team.test.js b/test/team.test.jsindex a871e44c..e9eaab75 100644--- a/test/team.test.js+++ b/test/team.test.js@@ -1116,6 +1116,7 @@ test('person-only moves are signed [E22,B26,H16]', { timeout: relayWorkBudgetMs(const shown = { id: 'G1', text: 'A row the person decides on the passkey.' };writeFileSync(join(box.root, 'SPEC.md'), readFileSync(join(box.root, 'SPEC.md'), 'utf8').replace('## G · Goals: what the client asked for\n',`## G · Goals: what the client asked for\n\n- G1 [draft, must] ${shown.text} | gate: review\n`));+ shown.source = readFileSync(join(box.root, 'SPEC.md'), 'utf8').split(/\r?\n/u).find(line => line.startsWith('- G1 '));const blind = { version: 1, type: 'person-request', id: randomUUID(), move: { verb: 'spec-approve', args: { ids: 'G1' } } };const seen = { ...blind, id: randomUUID(), rows: [shown] };for (const request of [blind, seen]) {