This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-2610100704270254 makes the sub-agent budget a repository setting; itd-2609151838312703 calls it a property of one machine

issuewontfixminoriss-2610262042504165

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

idiss-2610262042504165
typeissue
lifecyclewontfix
severityminor

References2

mentions1