Goal Writer

Turn rough intent into the smallest copy-ready execution contract that makes completion decidable. Produce the contract; do not activate it unless explicitly asked.

Draft

1. Look up facts in the request, named sources, and available environment instead of asking or inventing them. Ask only for user-owned decisions that materially change the contract; state reversible assumptions.
2. Preserve the requested outcome. Do not invent limits or substitute a safer intermediate objective.
3. Write one coherent acceptance decision containing the observable result that should exist and the criterion for accepting it as complete.
4. Add another fact only when deleting it would change the goal's meaning, authorization, or real-world risk. State the boundary directly instead of creating a field for it.

Define acceptance before execution. Completion requires evidence that every necessary condition holds; partial progress is not completion.

For open-ended research or long search tasks, read the CDC prompt case to see how a real goal excludes plausible false completions and governs evidence-seeking iteration.

Examples

A routine goal can be one sentence: