Skip to content

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.

Merge branch 'main' into codex/sol1122-20261025

Corey Olsone0a388595b03
diff --cc src/board.js
index 7ac3fe8d,5bb79ec8..9eddbc44
--- a/src/board.js
+++ b/src/board.js
@@@ -2342,4 -2340,19 +2340,20 @@@ export function approveOutside(board, i
/** Tailored inbox activity is the same canonical read projection as other board queries. */
export { agentActivity } from './board-query.js';
+export { recordRowVerification, rowVerifications } from './spec-verdicts.js';
+ /** Read recipient delivery state without mutating any cursor or receipt. */
+ export function activityDeliveryState(board, agentId) {
+ return activityDeliveryStore.activityDeliveryState(board, agentId);
+ }
+
+ /** Record the exact interrupts included in an authenticated recipient response. */
+ export function recordActivityDelivery(board, options) {
+ return activityDeliveryStore.recordActivityDelivery(board, options, { atomic, logEvent });
+ }
+
+ /** Record an explicit recipient acknowledgement separately from delivery. */
+ export function actOnActivity(board, options) {
+ return activityDeliveryStore.actOnActivity(board, options, { atomic, logEvent });
+ }
+ import { FLOW_SIZE_ENGINE } from './flow-size-engine.js';
+ import { submissionSize } from './submission-size.js';
diff --cc src/templates.js
index 1e26fbe9,0b604a86..f9d6edc7
--- a/src/templates.js
+++ b/src/templates.js
@@@ -106,8 -107,10 +107,12 @@@ On a board that is not set up, run \`pu
This repo runs on pullboard: a work board, lanes and a spec that live in git. Nothing ships until a second agent verifies it.
+ **Proof.** ${BOARD_PROOF_GUIDANCE}
+
**Source of truth.** \`SPEC.md\` holds every requirement as a row with an id, like \`G1.2\`. Code follows the spec. Commits cite the ids they serve: \`feat(scope): subject [G1.2]\`. Only a person approves or changes an approved row. Ids are permanent: a row the person cuts stays, marked \`wont\` (won't build), so every commit that cites it keeps its meaning. Propose each requirement with \`pullboard spec draft "<text>"\`; it returns the draft row id for the person to approve. To start from a blueprint's rules, questions and starter items, run \`pullboard blueprint add <name or file>\` (bundled: web-app); it files them all as drafts for the person to approve. Its questions file as pending rows, each with a default answer and its choices: the person answers one with \`pullboard spec answer <id> "<choice or text>"\` from the main checkout or the view, and the coordinator writes it with \`pullboard spec apply\`. Never answer a question by editing SPEC.md; spec check flags it. To share this board's approved rules and answered questions as a blueprint, run \`pullboard blueprint save [file]\`; it never writes items, notes, paths, emails or names.
++**Outside row verification.** A verifier from another parent session records an exact-row verdict with \`pullboard spec verify <id> accepted|rejected --reason "why"\`. The row's author cannot verify their own row. Read its recorded verdict with \`pullboard spec show <id>\`; verification does not approve or change the row.
++
**Blueprint starters.** To see which of a blueprint's starter items are on the board, run \`pullboard blueprint starters <name or file>\`; it names each filed item's id and status. \`pullboard init --blueprint <name> --verbose\` lists every row that waits for the person, doctrine rows included.
**Doctrine.** Our house rules for agentic development. This repo inherits Pullboard standard doctrine version 1. ${doctrine.repo ? doctrine.name : DOCTRINE_FILE} adds the repo's own rows, overrides a standard rule by its PB id, or declines it with a wont row and its reason as the row text: - PB7 [wont] <why>. Approved rows are in force; follow them as you would the spec. A rule with \`gate: check <command>\` and \`count: N\` holds a count that only falls: run pullboard doctrine check to see each count, and submit refuses RATCHET_ROSE when a touched rule rises or a changed file gains a problem. Lower \`count:\` in a commit when you fix problems; only the person raises it. Run pullboard spec --json to read the current merged rules. Re-run pullboard init after changing the doctrine to refresh this managed guidance.
diff --cc test/move-registry-baseline.json
index e29af028,dc7d7fa4..2b001382
--- a/test/move-registry-baseline.json
+++ b/test/move-registry-baseline.json
@@@ -63,8 -63,8 +63,10 @@@
"takeCoordinator",
"landingLeaseMove",
"recordPublishFinding",
+ "actOnActivity",
- "recordActivityDelivery"
++ "recordActivityDelivery",
+ "decideSpecRevisions",
+ "recordRowVerification"
],
"itemIdFirstArgument": [
"signBar",
@@@ -634,21 -634,21 +636,37 @@@
null,
null
],
+ "actOnActivity": [
+ null,
+ "first",
+ null,
+ null,
+ null,
+ null
+ ],
+ "recordActivityDelivery": [
+ null,
+ "first",
+ null,
+ null,
+ null,
+ null
++ ],
+ "decideSpecRevisions": [
+ null,
+ "first",
+ null,
+ null,
+ null,
+ null
+ ],
+ "recordRowVerification": [
+ null,
+ "first",
+ null,
+ null,
+ null,
+ null
]
},
"floorCases": [
@@@ -6969,11 -6974,9 +6992,14 @@@
"WRONG_LANE": "create a worktree in the required lane with pullboard worktree <lane> --model \"<model name>\", or take an item in your lane with pullboard next",
"EXCLUDED_REPOSITORY": "restore the GitHub origin of each excluded project, then run pullboard relay on --all",
"EXCLUDED_INVENTORY": "restore at most 256 excluded boards and their active paired devices, then run pullboard relay on --all",
+ "BAD_ACTIVITY_RECEIPT": "read your own inbox again and use its exact interrupt ids",
+ "ACTIVITY_NOT_DELIVERED": "read your own inbox before marking its interrupt acted on",
- "STALE_ACTIVITY_RECEIPT": "read inbox again; the claim changed before delivery was recorded"
++ "STALE_ACTIVITY_RECEIPT": "read inbox again; the claim changed before delivery was recorded",
+ "SPEC_REVISION": "refresh Needs you and decide the exact pending proposal",
+ "ROW_VERIFY": "pullboard spec show <id>, then pullboard spec verify <id> accepted --reason \"why\"",
+ "ROW_VERIFY_PROVENANCE": "draft the row through pullboard spec draft and join normally before verifying it",
+ "ROW_VERIFY_PENDING": "ask the coordinator to run pullboard spec apply before recording a verifier verdict",
+ "ROW_VERIFY_SELF": "ask an outside-parent verifier to run pullboard spec verify"
},
"replay": {
"initial": {