2026-10-03 — The machine's model-tier routing offer in `ahoy install` says abcd's proposal in counts, never one row per agent (ruling of the product thinker, 2026-10-03, relayed by the orchestrator of autonomous run A; applied by lane setupFit2; iss-2610031236155833). Asked: setup offers a plan giving each of abcd's 16 helpers a model level, and with all listed it cannot fit (options: counts only, split into parts, let it scroll, decide later). The answer, verbatim: "Show counts only". The question stays one yes-or-no answer; the counts are computed from the bundled proposal and the written table is unchanged; acceptance criterion 2 of itd-2609170822093401 is amended to match.

Frontmatter

.abcd/work/decisions/dcn-2610030000000004-the-machine-s-model-tier-routing-offer.md
open on GitHub ↗ · commit history ↗

mentions2

• iss-2610031236155833abcd's own setup questions break the asking limits its question check enforces. docs_target offers four answers and oracle_backend five, so with the decide-later answer they exceed the four options per question that the check and the host's question tool allow; and under the provisional row estimate artefact_kind (33 rows), docs_target (28), oracle_backend (43), scan_deep (25), visibility (30) and the machine routing offer (42) exceed 24 rows at 80 columns. TestEverySetupQuestionPassesTheLimits holds them as a baseline that may only shrink.
• itd-2609170822093401abcd proposes the model each agent deserves, and facilitates it where it can