Development record
itd-2609292107351737 treats refusing to start a run on a budget as abandoned ground from a superseded intent; the build ships a budget check that refuses a run whose estimate is over quota.
itd-2609292107351737 treats refusing to start a run on a budget as abandoned ground from a superseded intent; the build ships a budget check that refuses a run whose estimate is over quota.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-2609292107351737-every-development-session-records-what.md:57— "Budget enforcement: refusing to start a run on a budget is itd-29's superseded ground and is not revived here." - End B:
.abcd/development/brief/04-surfaces/34-build.md:258— "an estimate over the quota is refused at thebudgetcheck"
The draft says refusing to start a run on a budget belongs to superseded itd-29 and is not brought back. 34-build's start runs a budget check that compares the run's estimate with each runner's remaining quota and refuses the run at the budget check when it is over. A builder cannot treat budget refusal both as abandoned and as a shipped start check.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 712.
Frontmatter
| id | iss-2610262037171531 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262037171531-itd-2609292107351737-treats-refusing-to.md
open on GitHub ↗ · commit history ↗
References1
- itd-2609292107351737A development session's token cost is measured, and set against the size class its spec predictedrelated
mentions1
- itd-29Domain Experts Run A Spec Autonomously And Recover From Anything Without Touching Git