Claude ignores explicit approval gates defined in CLAUDE.md rules

Summary

Claude proceeds past explicit phase/approval gates defined in CLAUDE.md even when those rules are clearly stated and the model has read them.

Description

A project CLAUDE.md (and/or global ~/.claude/CLAUDE.md) defines a multi-phase plan structure with an explicit rule:

After completing each phase, stop and present findings to Frank for comment, note, or modification before advancing to the next phase. Do not run multiple phases back-to-back.

A companion memory file reinforces this:

At each phase boundary, present findings then stop completely; do not advance without Frank's explicit approval.

Despite both rules being loaded into context and acknowledged, Claude presented Phase 1 findings and then immediately closed Phase 1 and updated the handoff file — all without receiving an explicit approval from the user to do so. The user had to point out the violation.

Expected Behavior

After presenting phase findings, Claude should stop and wait for an unambiguous affirmative before taking any action that advances or closes the phase.

Actual Behavior

Claude autonomously closed Phase 1, updated the handoff file, and declared readiness for Phase 2 without waiting for explicit approval.

Impact

Users who define approval gates in CLAUDE.md to enforce workflow discipline cannot rely on those gates being respected. This undermines the ability to use CLAUDE.md as a reliable governance mechanism for agentic workflows.

Reproduction

1. Define a CLAUDE.md rule requiring explicit approval before advancing between phases.
2. Ask Claude to complete Phase 1 of a multi-phase task.
3. Observe that Claude advances past the phase boundary without waiting for approval.