Answer A-306: a module G creates is held by the test budget, not by section 626

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 22:00:16 +01:00
parent 4eba1f451b
commit edb7030102
1 changed files with 3 additions and 0 deletions
@@ -492,3 +492,6 @@ the principle that settles it, cited as "design 47 G A-n".
  in the same order as before, whatever order the asks end in.
 - **A-305** (ADR 0227 rule 8, ADR 0240 rule 2; principle 7) The pipeline runner's process declares the health `unit`,
  as every other process of mesh-delivery does; `runner_health` stays a tool and judges nothing for the node-engine.
+- **A-306** (§626, §419; principle 7) A Go module that G creates has no count at a commit of main, so §626 does not
+  hold it; the test budget (at most 50 integration and 500 unit tests) does. A test added to a module that exists on
+  main counts under §626, a contract's generated `TestFixtures` included.