Development record
itd-39 extends a Python prompt-router hook; the ahoy chapter says every hook event command is a shim that finds and runs the abcd binary
itd-39 extends a Python prompt-router hook; the ahoy chapter says every hook event command is a shim that finds and runs the abcd binary
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/01-ahoy.md:663— "resolving shim rather than a plain binary call." - End B:
.abcd/development/intents/planned/itd-39-scope-aware-memory-retrieval.md:33— "hooks/prompt_router_hook.py(itd-3) is extended from rules-only to rules + memory"
itd-39 scopes memory recall as extending hooks/prompt_router_hook.py (itd-3) from rules only to rules plus memory. The ahoy chapter describes the shipped hook manifest: nine event types, each event command a resolving shim rather than a plain binary call, with UserPromptSubmit provisioning the plugin-root binary when it is missing. So the prompt router that hook runs is the abcd binary. The planned work names a hook file the shipped surface does not have.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 373.
Frontmatter
| id | iss-2610262033124129 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262033124129-itd-39-extends-a-python-prompt-router.md
open on GitHub ↗ · commit history ↗
References1
- itd-39abcd Surfaces the Right Memory at the Right Momentrelated
mentions1
- itd-3abcd Loads Its Own Rules On Demand