Development record
itd-6 rules out direct provider integrations and sends everything through RP; the reading chapter routes a cold-reading position straight to a configured provider through abcd's own tier routing
itd-6 rules out direct provider integrations and sends everything through RP; the reading chapter routes a cold-reading position straight to a configured provider through abcd's own tier routing
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/23-reading.md:365— "when the person'soracle.roles.cold-reading-<position>points at a provider it sends the position's definition as the instructions and the parked bundle" - End B:
.abcd/development/intents/shipped/itd-6-rp-mcp-only-integration.md:54— "Direct OpenAI / Google / Anthropic API integrations — out of scope; route everything through RP"
itd-6 rules out direct OpenAI, Google and Anthropic API integrations and says to route everything through RP, with no abcd-side oracle selection. The reading chapter has abcd resolve a model-tier route per agent from layered oracle-routing tables. When oracle.roles.cold-reading-<position> names a provider, the ingest's dispatch form sends the definition and bundle directly to that provider and ingests the answer. abcd choosing a provider and calling it directly is what itd-6 excludes.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 680.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. itd-6's 'route everything through RP' was ruled when RepoPrompt was the only backend; later ADRs make the model host-delegated by default with opt-in adapters and the reading ingest follows them.
Frontmatter
| id | iss-2610262036529540 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262036529540-itd-6-rules-out-direct-provider.md
open on GitHub ↗ · commit history ↗
References1
- itd-6RepoPrompt over MCP is one opt-in reviewer route, beside the host's own agentsrelated
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.