scoville-planlisted

# Scoville Plan Maintain repository direction through direct Markdown and YAML edits. Preserve supported native `format_version: 1` behavior: setup, read-only recovery, Plans, Work Items, Decisions, proposals, lifecycles, blockers, evidence, and narrow repair. Require no CLI, MCP server, database, journal, or hidden state; remove or reinterpret no project-knowledge feature. A record does not prove work. On explicit opt-out: read no references; do not create or change planning files; make no Skill-derived claims. Report any exact conflict with a higher-priority project instruction requiring this Plan system. ## Ownership and limits Precedence: 1. system, safety, and explicit current-request instructions; 2. repository instructions and their canonical planning mechanism; 3. an existing supported native profile; 4. these defaults for gaps. Use the existing durable owner; never create a parallel Plan. Apply compatible guardrails only; runtime plans are disposable mirrors. Never invoke a planning CLI. The optional bundled validator is strictly read-only and structural, never a write path. Claim no locking, atomic publication, typed mutation, or semantic proof; report observations only. Family standalone: discovery != installed|active|applicable|required; absent|inactive => ignore/no require|install|simulate|reimplement; active+applicable => owner concern only, self continues; opt-out local. Owners: `scoville-brainstorm` divergence; `scoville-code-anti-ai-slop` engineering