Separate fixed requirements from flexible methods.
Clarifies which requirements must stay fixed and which implementation choices can change, producing an inspectable contract.
When to use it
Use when a request or instruction-bearing source may mix genuine requirements with one possible implementation; skip simple requests without meaningful method choices.
Give it a live request or an instruction-bearing source to audit; it refines a contract with you and includes a classification ledger for audits.
Requires mise to run the validation gate before using the named package resources.
The bundled package validator runs with python3.
Must be loaded before the first move to establish the private outcome map used by this workflow.
Must be loaded when the next action is text revision; it is not required for contract clarification alone.
No additional actions listed.