spk-doctrine-semantic-compression

Map the behavioral envelope first to identify protected behavior, then reduce duplication one concept at a time. Verify equivalence after each change and report evidence plus residual risk before considering the reduction complete.

Look for four redundancy types: exact, parameterized, structural, and semantic duplication. Extract one implementation per concept, consolidate competing paths behind a canonical owner, and only delete code proven to be dead.

Do not delete when the protected behavior is unknown or when verification evidence is unavailable for a non-trivial deletion. The Skill explicitly stops in these conditions to prevent accidental behavior changes.

Refactoring reduces or restructures code while preserving existing behavior, whereas feature expansion adds new behavior. This Skill stops if the request is actually feature expansion, since that falls outside behavior-preserving reduction.

Verify equivalence by comparing observable behavior against the mapped behavioral envelope, using tests or behavioral checks as evidence. Report the evidence gathered along with any residual risk that remains unverified.