Pearl_Architect

1. 1Invoke before any PR that touches 3+ subsystems
2. 2Ask it to verify a file path is canonical before building on it
3. 3Use it to resolve authority conflicts — it settles which doc wins
4. 4Always check with Pearl_Architect before adding a new config/*.yaml — it may already exist
5. 5Run it on PRs that add duplicate specs or root-level files

# Audit a PR before merge
act as pearl_architect — review PR #142 for subsystem drift

# Check authority on a file
pearl_architect: is scripts/manga/assemble_from_bank.py canonical or should it be in Pearl_Dev's scope?

# Resolve a conflict between two specs
pearl_architect: MANGA_V5_LAYERED_ARCHITECTURE.md and MANGA_LAYER_RENDER_CONTRACT_SPEC.md disagree on §4 — which wins?

# Register a new subsystem
pearl_architect: register new subsystem "social-video" under Pearl_Social authority

• Writing code — Pearl_Architect owns decisions, not implementation
• Replacing Pearl_Dev for CI gate authorship
• Being skipped on multi-subsystem PRs — drift that compound is expensive to undo