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(merge): decision hand-offs between boards carry one [B21,H16]

Corey Olsonf5478a87ad36
diff --cc docs/api.md
index 9daa737d,fdb40f2e..b4c1dcc9
--- a/docs/api.md
+++ b/docs/api.md
@@@ -678,4 -674,28 +678,30 @@@ A board-recorded item merge covers its
The JSON result includes `verification` entries with PR number, exact head, state, assurance, receipt identities, and any unverified commit IDs. GitHub statuses are shared by PRs with the same head: if an outside or unproven PR shares a commit with a proven proposal, the shared status stays red rather than lending the proposal's green status to it. Publishing observes and posts statuses; it never merges a PR or requires outside authors to use Pullboard.
+`pullboard why <file>[:<line>] --json` uses the `why file` catalog shape; this names the file form, not a literal `file` argument. It traces commits on the repository's actual primary branch, then resolves their item trailers, served row IDs and answered decisions in one board query. The legacy `why <id>` shape is unchanged. Answered decisions carry their recorded origin, statement, rationale, decider and relayer; absent historical provenance remains `unknown`. Row and item origins are also `unknown` unless recorded, rather than inferred from a related decision. An agent may label a relayed or inherited answer but cannot use that label to mint a person-origin record. Unproven original decider identities remain unknown, with the answering relay seat recorded separately.
++
+
+ ### Cross-board decision handoffs
+
+ `decisionHandoffs(db, { boardId, authorize })` in `src/decision-handoff.js` is
+ an I-D persistence port, not an aggregation CLI or a board-name resolver.
+ Each participant supplies its own SQLite connection, opaque immutable board ID,
+ and existing authority adapter. Call mutations inside the caller’s ordered
+ write boundary. No transaction or database connection spans boards.
+
+ `deliver(handoff, options)` checks the exact version-1 wire shape and original
+ option-set digest, then asks `authorize("disclose", handoff)` and, for answers,
+ `authorize("answer", handoff)`. The adapter must authenticate the requester,
+ source decision, destination, question, option digest and answer; a supplied
+ opaque authority value alone grants nothing. Accepted deliveries persist before
+ returning. Transport retries the returned wire independently at the other board.
+ Changed correlation or a conflicting answer refuses; late questions preserve
+ answers. `optionsDigest(options)` hashes a unique option set independent of order.
+
+ `query(source, participants, authority)` requires source-board read authority
+ for the exact namespaced reference and participant set. It returns
+ `{ complete, agreed, answers }`; callers must not act on an incomplete or
+ disagreeing result. Each destination contributes at most one answer, and a
+ query cannot omit a destination already recorded for that source decision.
+ This contract stores and returns answers to the source/requester’s authorized
+ query; it does not execute the decision or grant cross-board authority.
diff --cc src/next-step-defaults.js
index a6c017b9,49905b29..607de6c9
--- a/src/next-step-defaults.js
+++ b/src/next-step-defaults.js
@@@ -1,6 -1,8 +1,9 @@@
/** General CLI recovery text; operation-owned codes live in src/moves/ [P4,C7]. */
export const DEFAULT_NEXT_STEPS = Object.freeze({
+ "SHOUT_SPACES": "rewrite the shout with spaces between words, then send it again",
+ "DECISION_HANDOFF_BINDING": "use the exact versioned handoff, namespaced source decision and original option set",
+ "DECISION_HANDOFF_AUTH": "obtain authority for this exact question, answer or source query",
+ "DECISION_HANDOFF_CONFLICT": "use the recorded answer or create a new source decision",
"GIT_SYNC_LOG": "restore the append-only refs/pullboard/board history on origin before running pullboard sync",
"GIT_SYNC_REMOTE": "restore read/write access to origin, then retry the original command or run pullboard sync; keep its pending sealed move",
"GIT_SYNC_LOCAL_CHANGED": "run pullboard export to preserve local moves, then ask the coordinator to reconcile the local and remote prefixes before syncing",