phantom-hook-references-create-false-enforcement-confidence
MEMORY.md Tier 1 Directive 0 and master-orchestrator both referenced startup-routine-gate and brainstorming-gate as automated enforcement hooks, but neither existed in settings.json or on disk. This created false confidence that the behavior was enforced. The pattern: document only hooks that are verifiably registered — every hook claim must be traceable to a settings.json entry.
Related
- phantom-hook-refs-in-memory-cause-false-trust
- phantom-hooks-referenced-but-not-registered
- helix-phantom-hooks-startup-brainstorming-gates
- phantom-hooks-referenced-in-docs-not-in-settings
- 2026-04-04-oracle-001-self-architecture-analysis
- phantom-hook-references-create-documentation-drift
- phantom-hook-references-break-behavioral-mandates
- hooks-registry-drifts-silently-from-settings-json