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.

feat(guidance): make board receipts the proof [I1,I3,V4]

Corey Olson10a766b01856
diff --git a/src/agent-proof-guidance.js b/src/agent-proof-guidance.js
new file mode 100644
index 00000000..c8cfb007
--- /dev/null
+++ b/src/agent-proof-guidance.js
@@ -0,0 +1,4 @@
+/** The board owns proof; generated agent instructions never prescribe a separate evidence system [I1,I3,V4]. */
+export const BOARD_PROOF_GUIDANCE = "The frozen check, the gate and the verifier's verdict are the proof. "
+ + 'Do not keep private evidence folders, packets, manifests or custody rules. '
+ + "Cite the board's receipts. If those runs cannot decide the item, ask the coordinator to sharpen its bar.";
diff --git a/src/hooks.js b/src/hooks.js
index 91ba3be8..1873b121 100644
--- a/src/hooks.js
+++ b/src/hooks.js
@@ -1,3 +1,4 @@
+import { BOARD_PROOF_GUIDANCE } from './agent-proof-guidance.js';
/**
* The checks git runs (C1–C3, L3, L4): the commit message cites the spec, a lane's worktree stays in
* its folders, no secret or env file is committed, and a push sends exactly what the gate checked.
@@ -793,6 +794,7 @@ export function hookScript(hook, version = installerVersion()) {
return [
'#!/bin/sh',
`# ${HOOK_MARK}: runs the pullboard ${hook} checks. Edit pullboard.json, not this file.`,
+ `# ${BOARD_PROOF_GUIDANCE}`,
`want='${version}'`,
...(hook === 'commit-msg' ? ['message="$1"'] : []),
'root=$(git rev-parse --show-toplevel)',
diff --git a/src/templates.js b/src/templates.js
index 1e26fbe9..cef1ebb7 100644
--- a/src/templates.js
+++ b/src/templates.js
@@ -1,3 +1,4 @@
+import { BOARD_PROOF_GUIDANCE } from './agent-proof-guidance.js';
/**
* What `pullboard init` writes into a repo: the config, a starter spec, and the agent instructions
* every coding agent reads (AGENTS.md, which CLAUDE.md points at).
@@ -106,6 +107,8 @@ On a board that is not set up, run \`pullboard resume\` first. The coordinator w
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.
**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.