Development record
itd-5's lock-time pre-flight submits prompts to lifeboat-oracle; 01-agents' rosters have no such agent
itd-5's lock-time pre-flight submits prompts to lifeboat-oracle; 01-agents' rosters have no such agent
A sequencing impossibility (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/disciplines/itd-5-prompt-quality-additions.md:21— "the candidate prompt submitted tolifeboat-oraclefor clarity-rewrite" - End B:
.abcd/development/brief/05-internals/01-agents.md:23— "lifeboat-reviewer(disembark review),graveyard-interpreter"
itd-5's one-shot pre-flight sends each candidate prompt to lifeboat-oracle for a clarity rewrite. In 01-agents the lifeboat agent that ships is lifeboat-reviewer, which feeds disembark review and does not rewrite prompts. Neither 01-agents' shipped list nor its design-target roster names a lifeboat-oracle, so the pre-flight depends on an agent no document provides.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 816.
Frontmatter
| id | iss-2610262038457611 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262038457611-itd-5-s-lock-time-pre-flight-submits.md
open on GitHub ↗ · commit history ↗
References1
- itd-5Every Agent Prompt Carries Its Version, Earns Its Lock, And Survives Injectionrelated