Development record
itd-19's per-stage defaults set the oracle to in-session, rp or rp+codex; the oracle.review key accepts only host or rp.
itd-19's per-stage defaults set the oracle to in-session, rp or rp+codex; the oracle.review key accepts only host or rp.
A naming conflict (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-19-stage-aware-behaviour.md:31— "oracle=in-session (fast iteration)" - End B:
.abcd/development/brief/04-surfaces/34-build.md:544— "oracle.reviewin the layered configuration nameshost, the bundled default, orrp"
34-build gives the review route's values in .abcd/config.json as host (the bundled default) or rp, and refuses any fault in oracle.review before anything moves. itd-19 calls the same host route in-session and adds rp+codex. A stage default written from the draft would use a second name for the default route and a value the reader refuses.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 716.
Frontmatter
| id | iss-2610262037211310 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262037211310-itd-19-s-per-stage-defaults-set-the.md
open on GitHub ↗ · commit history ↗
References1
- itd-19Defaults That Match Where the Project Livesrelated
mentions2
- iss-2610262042426018itd-19's stage profiles switch one oracle value per stage; itd-2609170822093401 says that repo-wide value is read by nothing and routes per agent tier instead
- iss-2610262043485833itd-19 sets the oracle backend from the project's stage; itd-6 has ahoy lock it based on whether RP is reachable