outcome-bounded-work
Outcome-Bounded Work
Outcome
Shape a live conversation or audit an instruction-bearing artifact so the required result, proof, and safety stay fixed while replaceable implementation choices remain open.
Trigger and boundary
Use when a conversation, prompt, task, specification, plan, policy, or skill may mix true requirements with one possible way to satisfy them.
Do not use for a simple request with no material method choice. Do not weaken an exact method, explicit user requirement, or higher-priority rule. Use simplify-skill when the requested outcome is limited to simplifying a skill package.
Load starting-point before the first move through the host's skill-loading capability. It owns the private map of outcome, proof, constraints, starting path, and unknowns, plus the intervention gate for changing routes. This skill turns that map and the source instructions into an inspectable contract without taking over planning or execution.
Use conversation mode for live requests. Use artifact audit mode only when the user asks to inspect an existing instruction-bearing source.