Contracts describe exchanged durable facts. All current contracts are provisional unless an individual page says otherwise: additive optional fields are expected to be compatible; removed/changed required fields require a versioned migration. Producers must emit schema-valid, redacted data; consumers must validate required fields and tolerate unknown optional fields. Invalid examples and valid examples are machine-readable in schemas/contracts/examples.json and are checked in tests.
| Contract | Schema | Purpose |
|---|---|---|
| Work package | JSON Schema | Frozen scope and dependency contract |
| Task state | JSON Schema | Durable package execution state |
| Worker result | JSON Schema | Worker completion declaration |
| Validation result | JSON Schema | Mechanical check evidence |
| Event record | JSON Schema | Append-only event ledger row |
| Handoff packet | JSON Schema | Recovery/reassignment context |
| Merge decision | JSON Schema | Gate outcome with evidence |
| Supervisor action | JSON Schema | Recorded Hermes decision |
See compatibility policy and state migrations.