What problem does it solve? Keeping cross-project parity documentation honest is hard: docs drift from code, and teams may be tempted to weaken security invariants just to match another product's behavior. This Skill provides a disciplined workflow for maintaining CyClaw↔CG-agent-harness parity contracts without ever weakening harness invariants. ## Core Features & Use Cases - Drift Classification: Tags every parity claim as FACT (observed in harness code, config, or tests) or INFERENCE (suspected intent or stale prose), so PR bodies stay evidence-based. - Status Reporting: Runs scripts/parity-status.py and produces a structured PASS/DRIFT/BLOCKED report summarizing drifts and invariant preservation. - Hard Refuse Rules: Explicitly blocks opening harness gates (agentic.enabled, allow_git_write_tools, api_key_optional) or loosening invariant_guard checks to chase parity. - Use Case: After a CyClaw merge, run this Skill to refresh docs/parity/* ledgers, record intentional divergences (e.g., fail-closed gates, Seatbelt isolation) as FACT, and defer CyClaw product-policy questions to the Advisor instead of mutating harness code. ## Quick Start Ask the AI to run the parity workflow to check docs/parity ledgers against current harness code and report any drift.