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(doctrine): T6 holds at 18 after #1012 [D1,D3]
Corey Olson3b68b17a197d
diff --git a/DOCTRINE.md b/DOCTRINE.mdindex e8a8addb..167a14ca 100644--- a/DOCTRINE.md+++ b/DOCTRINE.md@@ -29,7 +29,7 @@ Statuses: approved = in force · draft = proposed · wont = considered and decli- T3 [approved, must] The suite passes on Node 22, 24 and 26 before a release. | gate: release check- T4 [draft, must] A check that guards a rule is shown failing on a broken copy before anyone trusts it. | gate: review- T5 [approved, must] Every test name cites the spec rows it proves; existing omissions can only fall. Why: a passing test must name the requirement it checks. | gate: check node bin/checks/test-names.js | count: 15-- T6 [approved, must] Tests declare the source files they read; existing omissions can only fall. Why: affected-test selection must see those dependencies. | gate: check node bin/checks/test-inputs.js | count: 19+- T6 [approved, must] Tests declare the source files they read; existing omissions can only fall. Why: affected-test selection must see those dependencies. | gate: check node bin/checks/test-inputs.js | count: 18- T7 [draft, must] A fix ships with a test that reproduces the original failure. Rigor names each fix commit that changes no test file, at the first line it changes; whether the test reproduces the failure is the root-cause-control rule. | gate: check node bin/pullboard.js rigor quality --rule fix-test | count: 0 | source: rigor-quality:fix-test- T8 [draft, must] A new gate or check has a test that fails closed when it has no data. Rigor names a new file under checks/ or gates/, or named *-check or *-gate, that no test changed in the same change names; whether that test feeds it no data and expects a refusal is review, since no command can read what a test asserts. | gate: check node bin/pullboard.js rigor quality --rule fails-closed | count: 0 | source: rigor-quality:fails-closed- T9 [draft, must] A guard test fails when the guard is deleted. Rigor turns each throw a change adds to a source file into a no-op, one at a time, and runs the test files the change touches; a guard they still pass without is named. | gate: check node bin/pullboard.js rigor quality --rule guard-mutation | count: 0 | source: rigor-quality:guard-mutation