Keep status needs_review until evidence is complete and contradictions resolved. This is trusted review material; never inject it wholesale into policy context. Generate machine fields with ora dev task-contracts template; see the authoring guide.
Identity and scope
- Backend/task, source revision, original public instruction/source:
- Predicate/helpers/reset/randomization and asset/frame hashes:
- Covered seeds/configuration/assets and excluded variants:
- Previous/candidate contract versions and hashes:
- Reviewer/date/status:
Source-to-public mapping
| ID | Private condition or original intent | Physical/frame interpretation | Public observability | Public clause | Reason for withheld or stronger semantics |
|---|---|---|---|---|---|
| <condition> |
Audit all quantifiers, roles, orientations, spatial relations, holding/release, contacts/joints and timing. Identify functional faces and rigid/articulated structure. Do not confuse final absolute orientation with relative rotation or a partial surface with whole-object shape.
Timing and evidence
- Event-latched, instantaneous or terminal verdict:
- Successful original evidence/hash and exact source/asset/configuration:
- Capture timing and conflict with proposed wording:
- Relevant near miss and distinguishing clause:
- Expert strategy deliberately excluded from requirements:
- Missing/contradictory evidence and disposition:
Public projection
Public completion contract for this task:
- <Source-supported observable completion clause.>
Exclude private thresholds, coordinates, GT, IDs, code and expert trajectories. Record forbidden known-wrong claims.
Feedback and delivery
| Case | Execution facts | Public stage/code | Message delivered | Valid recovery | Unsupported inference |
|---|---|---|---|---|---|
| <failure> |
- Rendered clauses and absence of private content:
- Default selection, RunPlan layer/disclosure and real per-round Native delivery:
- Both provider protocols, or explicit untested coverage:
- Failure fixtures: bounded reasons, unknowns, no cross-action/arm/round mixing:
- Source/asset/contract invalidation boundary:
- Separate conclusions for review completeness, hash binding, delivery and physical validity: