phantom-hook-refs-in-memory-cause-false-trust

MEMORY.md Tier 1 Directive 0 and master-orchestrator SKILL.md referenced startup-routine-gate and brainstorming-gate hooks that did not exist in settings.json or on disk. Operators reading these docs would assume automated enforcement was active when it was not. Any hook reference in documentation must be verified against the registered hooks list before publishing.

Related

• helix-phantom-hooks-startup-brainstorming-gates
• phantom-hooks-referenced-but-not-registered
• master-orchestrator-auto-routing-aspirational-not-wired
• master-orchestrator-auto-routing-is-aspirational
• clawteam-openclaw-multi-agent-swarm-evaluation
• phantom-hooks-referenced-in-docs-not-in-settings
• phantom-hook-references-create-false-enforcement-confidence
• phantom-hook-references-create-documentation-drift
• phantom-hook-references-break-behavioral-mandates
• hooks-registry-drifts-silently-from-settings-json