Development record
Implement says abcd calls no model; ahoy has a delegating verb send its step to a configured provider itself
Implement says abcd calls no model; ahoy has a delegating verb send its step to a configured provider itself
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/27-implement.md:507— "the model service only by the verdict of a canary agent the lead runs, since abcd calls no model" - End B:
.abcd/development/brief/04-surfaces/01-ahoy.md:204— "A delegating verb whose agent'soracle.rolesentry points at a configured provider sends the step there itself"
27-implement probes the model service only through a canary agent the lead runs, and gives the reason that abcd calls no model. 01-ahoy says a delegating verb whose agent's oracle.roles entry points at a configured provider sends the step there itself, so abcd does call a model whenever a provider is configured. The premise the outage probe rests on is false in that case.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 285.
Frontmatter
| id | iss-2610262032338974 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262032338974-implement-says-abcd-calls-no-model-ahoy.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-261026203741032827-implement says the model service can only be probed through a canary agent because abcd calls no model; itd-166 records every model call abcd makes