Development record
2026-10-22 — The status-branch ruleset is applied by the person by hand, by design, and C15 is corrected to say so (facilitator, on the delegation of 2026-10-14; iss-2610222040438015, itd-2609151838312703): every ruleset in .abcd/work/rulesets is applied by the person with the README's gh api command and refreshed into the mirror, and invariant 10 lets abcd change a remote only through a dedicated, confirmed apply verb, which no record ever planned for rulesets; so C15's last clause, 'applied through the rulesets' own apply verb', was a drafting slip, not a promise owed, and becomes 'applied by the person from that mirror'. The outcome C15 asks for (the forge refuses deletion and force-push under abcd-status/) is unchanged and live as ruleset 25302453. A verb that applies or verifies rulesets would belong with the branch-protection doctor draft (itd-92), not here (grounds: .abcd/work/rulesets/README.md; brief invariant 10; adr-44)
2026-10-22 — The status-branch ruleset is applied by the person by hand, by design, and C15 is corrected to say so (facilitator, on the delegation of 2026-10-14; iss-2610222040438015, itd-2609151838312703): every ruleset in .abcd/work/rulesets is applied by the person with the README's gh api command and refreshed into the mirror, and invariant 10 lets abcd change a remote only through a dedicated, confirmed apply verb, which no record ever planned for rulesets; so C15's last clause, 'applied through the rulesets' own apply verb', was a drafting slip, not a promise owed, and becomes 'applied by the person from that mirror'. The outcome C15 asks for (the forge refuses deletion and force-push under abcd-status/) is unchanged and live as ruleset 25302453. A verb that applies or verifies rulesets would belong with the branch-protection doctor draft (itd-92), not here (grounds: .abcd/work/rulesets/README.md; brief invariant 10; adr-44)
Frontmatter
| id | dcn-2610222105036844 |
|---|---|
| type | decision |
| date | 2026-10-22 |
.abcd/work/decisions/dcn-2610222105036844-the-status-branch-ruleset-is-applied-by.md
open on GitHub ↗ · commit history ↗
mentions4
- adr-44abcd never mutates a remote uninvited, and identity derives from caller-local facts
- iss-2610222040438015spc-2610150728396006's C15 says the status-branch ruleset (.abcd/work/rulesets/status-protection.json) is applied through the rulesets' own apply verb (invariant 10), but abcd has no such verb: the ruleset was applied by hand on 2026-10-17 with gh api (it is live as ruleset 25302453), the way the rulesets README tells a person to; so the criterion names a mechanism that does not exist and cannot be checked as written
- itd-92abcd tells every repo the truth about its fence
- itd-2609151838312703Sessions under any account, on any machine or in the cloud announce what they are doing through short fixed-form announcements on the shared remote, a person reads everyone's status with one command, and what is really a hold stays a reservation