cascade-dedup

# Cascade dedup ## Contract | Field | Bound contract | |---|---| | Trigger | Prompt-doctrine duplication, drift, or conflict across the cascade family. | | Authority | Human-only. Require explicit human invocation; preview the target and consequence before rewriting prompt doctrine at rest, bumping the catalog `releaseVersion`, or editing authorized external harness embeds. | | Side effect | Rewrites cascade prefixes/tails, bumps the catalog `releaseVersion` and re-renders package surfaces, and edits authorized external embeds. | | Done | All canonical tails match, every strip is evidenced, divergence ledger complete, verification green. | ## Inputs - The canonical baseline file `system-prompt-baseline.md` — must exist and be the agreed source of truth. - The six output-style embeds: `packages/odin-core/output-styles/{axiom-mode,builder,duet,linus,odin,benchmark}.md`. - The two external harness embeds: `~/.omp/agent/AGENTS.md` and `~/.codex/AGENTS.md`. - Explicit user authorization, recorded in the run, before any `benchmark.md` tail repair or authorized external embed edit. ## Procedure 1. **Map the cascade family and zones.** The canonical baseline `system-prompt-baseline.md` is the whole-file source of truth and wins every conflict. For each output-style embed (`axiom-mode`, `builder`, `duet`, `linus`, `odin`, `benchmark`), the persona prefix above the charter `<role>` (the second `<role>` in each file) is the strip zone. The tail from the charter `<role>` to EOF is ...