# Define-task contract rubric

Review the Task Contract against these questions:

1. What observable result belongs in `objective`?
2. Which concrete artifacts or state changes belong in `expectedOutputs`?
3. Which binary or measurable checks belong in `acceptanceCriteria`?
4. Which scope boundaries, prohibitions, or required conditions belong in `constraints`?
5. Does execution require an approval, dependency, credential, or user decision that must be
   represented before work starts?
6. Is there already a matching Task that should be inspected or refined instead of duplicated?
7. Should the Task be captured for later or explicitly started now?

Prefer inspectable evidence: a test passes, an artifact exists, a measured threshold is met, a report
supports a named decision, or a reviewer accepts stated criteria.