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(bar): explain named baseline reporter requirements [V2,P4]
Corey Olson40b4e9682770
diff --git a/docs/formats.md b/docs/formats.mdindex 10467cbf..24779325 100644--- a/docs/formats.md+++ b/docs/formats.md@@ -210,7 +210,7 @@ Engine 85 also adds `recordLandingTestDefect`. A red batch whose bisection findsEngine 90 records the parent session a seat joined under and stamps each verdict with its assurance: independent when the builder's and reviewer's recorded parents differ, procedural when either is unknown (#1102). Review eligibility, next and the queue exclude any seat sharing a parent with an author. Older engines replay their recorded verdicts with no parent recorded.-`BAR_READY_ENGINE` introduces ordered `setBarReady` and `signBar` moves; its unassigned leaf is numbered by the landing merge. Readiness defaults off. `pullboard bar ready on` is coordinator-only and snapshots already-frozen bars, which remain grandfathered until their words change. Older engine moves retain their recorded behavior. Enabling readiness makes later bars require an observed main-red named case (including an absent named case), `Named test:`, `Measurements:` and `Reviewer edges:` sections, and an outside-parent signature. Section presence is enforced; the signer judges whether the methods and edge cases are adequate.+`BAR_READY_ENGINE` introduces ordered `setBarReady` and `signBar` moves; its unassigned leaf is numbered by the landing merge. Readiness defaults off. `pullboard bar ready on` is coordinator-only and snapshots already-frozen bars, which remain grandfathered until their words change. Older engine moves retain their recorded behavior. Enabling readiness makes later bars require an observed main-red named case (including an absent named case), `Named test:`, `Measurements:` and `Reviewer edges:` sections, and an outside-parent signature. Section presence is enforced; the signer judges whether the methods and edge cases are adequate. The named-case witness currently reads captured TAP or JUnit case records with per-case timing. Configure the project’s own reporter to emit those records to the captured output; a pretty summary or an XML file that is never emitted does not establish a named failure. Unsupported output remains unknown and refuses readiness, rather than inferring a named failure from the process exit. This opt-in evidence requirement does not change ordinary workflow with readiness off.Semantic add/edit moves capture the current native author session and parent in their ordered arguments, preserving authors of unchanged fields. Signing likewise captures the current signer; replay never consults a replica's environment. A current session's explicit joined parent is used when native parent metadata is unavailable. Taking over a known helper seat without current parent metadata refuses rather than declaring that helper independent. Unknown historical agent identities cannot establish independence. The authenticated person has `authority: "person"`, with null session and parent, and is a distinct authority: an agent may sign a person-authored bar and the person may sign an agent-authored bar. Unknown agent authors still fail closed. Terminal person actions use `--as person` on `add`, `edit` or `bar sign`; the authenticated coordinator view records that authority directly. Ordered transport selects person credentials for this provenance, while retaining normal agent credentials for agent authors; no parent is invented for the person. These captures do not rewrite historical seat identity. Each `bar-revision` event binds the exact title, criterion, check, brief, citations, dependencies and route; `bar-sign` additionally binds its event revision, baseline digest, coverage plan, author parents, signer and note. Editing away and back still requires a new signature. Additive `board_meta` keys `bar_ready_setting`, `bar_grandfather:<id>`, `bar_revision:<id>` and `bar_sign:<id>` hold the current indexes; the events retain history.diff --git a/src/bar-readiness.js b/src/bar-readiness.jsindex e964a780..a0170946 100644--- a/src/bar-readiness.js+++ b/src/bar-readiness.js@@ -104,7 +104,7 @@ export function barReadiness(board, item, { signature = true } = {}) {const evidence = baseline?.testEvidence;const namedRed = witness && evidence && !evidence.passed.some(name => name.includes(witness))&& (evidence.failed.some(name => name.includes(witness)) || evidence.noTestsMatched && item.item_check.includes(witness));- if (!baseline || baseline.result !== 'red' || baseline.command !== item.item_check || !baseline.main || !namedRed) missing.push('a recorded red check baseline at main for the Named test (an absent named case counts; unrelated shell failures do not)');+ if (!baseline || baseline.result !== 'red' || baseline.command !== item.item_check || !baseline.main || !namedRed) missing.push('a recorded red check baseline at main for the Named test (emit named TAP/JUnit cases with timing; an absent named case counts, unrelated shell failures do not)');if (!notes.measurements) missing.push('Measurements: a method beside each quantitative bound, or an explicit statement that there are none');if (!notes['reviewer edges']) missing.push('Reviewer edges: cases a reviewer should try');if (!revision || revision.digest !== barDigest(item)) missing.push('a recorded current bar revision (edit the brief)');