Development record
The oracle-routing intent sends a step to a configured provider that can serve its tier, but the adapters page says a tier alone never reaches a provider
The oracle-routing intent sends a step to a configured provider that can serve its tier, but the adapters page says a tier alone never reaches a provider
A premise contradiction (severity major) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-2609170822093401-the-oracle-choice-is-one-repo-wide-value.md:105— "provider where reachable and able to serve the tier" - End B:
.abcd/development/brief/05-internals/02-adapters.md:129— "tier: it is reached by a role or a judgement type pointed at it, never by a tier"
itd-2609170822093401 matches the winning row's tier against the machine's connections and uses a provider wherever it is reachable and able to serve the tier, so economy rows run on a local server without anyone touching a row. The adapters page says a provider claims no tier: it is reached only by a role or judgement type pointed at it, and that role wins whatever tier the routing tables name. The two documents cannot both describe how a step reaches a provider, and the intent's central mechanism is the one the shipped adapter rules out.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 859.
Deferral 2026-10-27
Deferred past v0.15.1: Deferred by the product thinker on 2026-10-27 (dcn-2610271112330536): the brief's single-home rewrite (dcn-2610271112339516, dcn-2610271112330235) rewrites or removes most of the passages this record quotes.
Frontmatter
| id | iss-2610262039253719 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | major |
.abcd/work/issues/open/iss-2610262039253719-the-oracle-routing-intent-sends-a-step.md
open on GitHub ↗ · commit history ↗
References1
- itd-2609170822093401abcd proposes the model each agent deserves, and facilitates it where it canrelated
mentions4
- dcn-26102711123302352026-10-27 — The product thinker ruled on 2026-10-27 that the design brief shows the target design, in the present tense, with a status tag where a part is built, rather than the shipped state. With the ruling that behaviour lives in the command pages, the brief holds the product as aimed for and why, and the command pages hold what abcd does today. This reverses itd-147's currency rule, so a superseding ADR is owed, and the brief's checks are rebuilt around the status overlay.
- 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.
- dcn-26102711123395162026-10-27 — The product thinker ruled on 2026-10-27 that each abcd command's behaviour is written once, in its command page, which agents follow when they run it. The brief's chapter for the command keeps why the command exists, its trade-offs and why it refuses what it does, with its sub-verb table and generated appendix, and points to the command page for behaviour. The documentation-fidelity check moves to the command pages. This reverses the behaviour half of adr-2609231028044006 and invariant 18, so a superseding ADR is owed.
- iss-2610262044285635Tier routing sends a row to a provider that can serve its tier, but the shipped adapter rules that no provider serves any tier