iurykrieger/claude-yoke/contracts

Sprint contracts

Co-written by the Implementation Agent and the Validation Agent

when they reach consensus on a sub-objective interpretation.

Sprint contracts can refine the Acceptance Contract envelope but

never relax it. A contract that contradicts the Acceptance Contract

pauses the loop for human arbitration (Trigger 4 in Sprint 6+; in

v0.4.0 the loop pauses with a clear message).

Contract <id>

• id: "<short identifier, e.g. c1>"
• topic: "<ambiguity that was resolved>"
• decision: "<the agreed interpretation>"
• rationale: "<why this resolution; cite the Acceptance Contract criterion>"
• timestamp: "<iso8601>"
• agents_involved: [implementation, validation]
• references:
• "acceptance-contract.md#<criterion id>"
• cycle: <N>

<!-- Subsequent contracts append below this line, one ## Contract <id> block per consensus reached. -->

<!-- The schedule_next: field on each contract entry was retired by the sensor-harness-realignment refactor (PRD 2026-04-30-sensor-harness-realignment). The Validator no longer emits schedule_next:; per-cycle cost-based filtering moved to the coordinator (/yoke:implement) via --max-time-cost / --max-token-cost on verify-acceptance.sh. New contracts MUST NOT include the field; legacy entries can stay verbatim for audit but are not re-read. -->