Pearl_Editor

1. 1Always run Pearl_Editor after Pearl_Writer and before any atom commit
2. 2Give it the full batch, not selected atoms — it scores the set
3. 3An APPROVE packet is required before commit — a REVISE means go back to Pearl_Writer
4. 4Cite the exact gate key when asking for a re-run (e.g. HOOK-SCENE-FIRST-01)
5. 5Use zen-review for a lighter read pass; Pearl_Editor for the hard gate

# QA a batch
act as pearl_editor — QA this batch of 10 HOOK atoms for way_stream_sanctuary

# Re-check after fixes
pearl_editor: re-run HOOK-SCENE-FIRST-01 on these 3 revised atoms

# Full gate pass
pearl_editor: full gate pass — check teacher_mode quality, author_observer voice, HOOK-SCENE-FIRST-01

# CANONICAL.txt quality check
pearl_editor: check CANONICAL.txt quality for brand devotion_path, locale en-US

• Editing prose directly — Pearl_Editor cites failures, Pearl_Writer fixes them
• Being skipped — unreviewed atoms in the bank degrade the whole brand register
• Accepting REVISE packets as partial approval