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
Merge branch 'main' into core/878-claude
Corey Olson19c6389b8299
diff --cc docs/formats.mdindex 5fe9ef0d,e6ad792d..90751d33--- a/docs/formats.md+++ b/docs/formats.md@@@ -148,8 -148,6 +148,8 @@@ Engine 42 adds ordered `recordHealthFinEngine 52 reopens an accepted item that conflicts with the trunk for a main merge. A `reopen` move may carry `conflict: {files, trunk}`: the files that conflict, and the full trunk commit they conflict with. The CLI takes one exact path per `--conflict <file>` flag and splits or trims nothing inside it, so a path with spaces or commas is named as Git reports it in `git merge-tree --write-tree --name-only -z`; `files` holds those exact paths, nonempty and without NUL. The CLI fills `trunk` from Git and refuses `NOT_CONFLICTING` when the accepted commit merges cleanly, or `CONFLICT_FILES` when a named file is not one Git reports as conflicting. The board refuses `NOT_ACCEPTED` unless the item is verified with an accept at its commit, and `BAD_CONFLICT` for a malformed conflict. A conflict needs no note and no landing failure; the event records `supersedes`, the accept it sets aside, `conflict`, and `cause: "refusal:MERGE_CONFLICT"`, never `landingFailure`, so rigor counts it as a merge conflict and never as a failing test. The item reads `needs main merge` until its next verdict, and the re-review checks the frozen check at the new head. A `reopen` move carrying `conflict` requires engine 52, and older engines refuse it with `RELAY_MOVE` before changing their board or cursor; a board replaying an older engine refuses it with `ENGINE_VERSION`. Moves recorded under engines 51 and earlier replay unchanged. The unlanded feature’s previous allocations were 36 and 47; it moved to 52 after the trunk reached engine 50 and milestone withdrawal was allocated engine 51, preserving every landed feature’s engine.- Engine 55 (`ROW_DRAFT_ENGINE`) adds `draftSpecRow`: an agent in a lane worktree records a drafted spec row on the board, since SPEC.md is the coordinator's file and a lane cannot write it. The move carries `row: {id, text, gate, tier, section}`; the sender plans the id across SPEC.md, the doctrine file and the board's earlier drafts, and the board refuses `ROW_ID_TAKEN` for an id it already holds. Until spec apply writes it, the commit-msg hook and `spec check` read a board draft as a draft row, so a lane cites the returned id at once and its worktree stays clean. The coordinator's `spec apply` writes each pending board draft into SPEC.md at its own id, and the person approves it there as before; a draft counts as applied once SPEC.md has its id. A move carrying `draftSpecRow` requires engine 55, and older engines refuse it before changing their board or cursor. Engines 53 and 54 are allocated to other changes.++Engine 55 (`ROW_DRAFT_ENGINE`) adds `draftSpecRow`: an agent in a lane worktree records a drafted spec row on the board, since SPEC.md is the coordinator's file and a lane cannot write it. The move carries `row: {id, text, gate, tier, section}`; the sender plans the id across SPEC.md, the doctrine file and the board's earlier drafts, and the board refuses `ROW_ID_TAKEN` for an id it already holds. Until spec apply writes it, the commit-msg hook and `spec check` read a board draft as a draft row, so a lane cites the returned id at once and its worktree stays clean. The coordinator's `spec apply` writes each pending board draft into SPEC.md at its own id, and the person approves it there as before; a draft counts as applied once SPEC.md has its id. A move carrying `draftSpecRow` requires engine 55, and older engines refuse it before changing their board or cursor. Engine 54 is the strong-rejection notice above; engine 53 is allocated to another change.+The CLI declares its engine in every relay request's `X-Pullboard-Engine` header.A linked board requires at least engine 48 after issuing any agent token or machine credential, includingrevoked or expired ones; before engine 48 these minimums were 3 and 6. The minimum survives reopening the auth database;diff --cc src/machine.jsindex c6241dd2,39f29674..51d7b53a--- a/src/machine.js+++ b/src/machine.js@@@ -17,12 -17,11 +17,15 @@@ export const WITHDRAW_MILESTONE_ENGINE/** First engine that automatically escalates an item's second rejection at its current route [B15]. */export const AUTO_ESCALATE_ENGINE = 50;+/** The first engine that records a spec row a lane agent drafts on the board, not in SPEC.md (#878). */+export const ROW_DRAFT_ENGINE = 55;++ /** First engine replacing an automatic ceiling escalation with a paired notice [B15,H16]. */+ export const STRONG_REJECTION_NOTICE_ENGINE = 54;+/** Executable move semantics, carried by every sealed move and retained during replay [H16]. */export const ENGINE_VERSION = Math.max(+ ROW_DRAFT_ENGINE,AUTO_ESCALATE_ENGINE,RIGOR_NOTICE_ENGINE,WITHDRAW_MILESTONE_ENGINE,