09 — The first increment, built and run
Summary
Run on 3 September in a scratch clone with both hooks installed and every event marked as a test lane. A 400 KB commit was refused by pre-commit with the exclusion's reason printed and HEAD unmoved; the eleventh commit of the day was told a draw was recorded, seventeen of eighteen left because the reserve holds ten per cent back; a push to main was refused by the mandate before a byte was counted and a push to a permitted branch succeeded in the same minute. Then the whole requested-draw workflow: refused, a request with an id, a decision, a retry that drew via it, and a commit that carried its own two claims. Then exhaustion at the fifth reading, with the earlier escalation found already waiting, and a commit inside the band still proceeding. Five findings, including that a test lane needs its own balance, found because the first run of the eleventh commit reported nothing.
Key concepts
- The acceptance log — every number on the page is copied from it
- A commit carries its own claim — IE-D12
- Setting, not boundary — the same tier the two enforcement points before it reached
Key ideas
- exit=1 is git's, from a hook that ran before the commit object existed.
- The count pool drew three times on an ordinary session; the rating rule will say the band is wrong, which is the loop working.
- Nothing on GitHub was refused: the remote was a folder, the hooks and the refusals were real.