Development record
itd-2610100704270254 makes the sub-agent budget a repository setting; itd-2609151838312703 calls it a property of one machine
itd-2610100704270254 makes the sub-agent budget a repository setting; itd-2609151838312703 calls it a property of one machine
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-2610100704270254-an-abcd-run-works-out-how-many-sub.md:18— "The repository's own config sets the budget, eight of the middle model class by default as abcd ships it" - End B:
.abcd/development/intents/planned/itd-2609151838312703-sessions-announce-what-they-are-doing.md:97— "the machine cap is a property of one machine, and hosted sessions run on their own."
itd-2610100704270254 has the repository's own config set the budget, with abcd's bundled default. itd-2609151838312703 keeps the same budget out of its scope because the machine cap is a property of one machine. The two records disagree on which layer owns the setting.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1097.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): the two ends do not conflict when read in full. The planned intent's line is a scope boundary ('sits beside this intent, not in it') rather than a rule on which layer owns the setting; the shipped pace settings already layer flag, repository, machine, bundled, which is the likely answer.
Frontmatter
| id | iss-2610262042504165 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262042504165-itd-2610100704270254-makes-the-sub-agent.md
open on GitHub ↗ · commit history ↗
References2
- 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 reservationrelated
- itd-2610100704270254An abcd run sets how many sub-agents it keeps alive by the models they run onrelated
mentions1
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.