The updated schema for Handover, with the diagram of the field kit and the diagram of the graph on one page. Tap any part of either diagram to see exactly where it lives in the schema.
A field kit is the reusable playbook for one field. A graph is how a run orders its work: units, links, splits, and joins. The schema describes both, and this page is drawn from data that validates against it.
The machine-readable contract. One file, two definitions: $defs/fieldKit and $defs/graph (with $defs/unit).
The interactive diagram page. Same content as this artifact: tap the kit parts and the graph nodes, read the schema underneath each one.
Handover v4. Step 5 defines the field kit. The Graph section (items 1 to 8) defines the graph. The schema follows the skill, never the other way round.
Kit fields in total: 12 required, 4 optional, in $defs/fieldKit.
Required fields per unit: name, output, owner, check, passes. No output file means not a unit.
Field that ever changes while a run works: passes, false to true, per unit.
Canonical location of the schema file in the repo.
Matches Handover v4, skills/local-handover/SKILL.md.
Three definitions. Graph units point back to unit with $ref.
anyOf: [ { required: ["fieldKit"] }, { required: ["graph"] } ], a file with neither a kit nor a graph is not a Handover file. A file with both is the normal case: the kit that runs, and the graph it runs as.Proof status is part of the schema, not a boast: proofStatus is an enum, "proven" | "draft" | "proof failed". One passing task does not establish coverage of a field, and a generated kit that was never executed is a draft.
graph.decision = { mode: "graph", reason: "…" }"graph" because the job splits into parts with no dependency between them, some parts depend on others, and a later part needs both. Loop alone is the default for one straight line with one deliverable. The reason is always written in the graph file.
| Unit (name) | Output | Owner | Check | dependsOn | passes |
|---|
This is the same shape as skills/local-handover/units-template.json, extended with dependsOn from the graph definition. The template in the repo is the minimal starting file; the schema above is the full contract.
| On the diagram | Schema path | Rule it carries |
|---|---|---|
| Kit tile: Router | $defs/fieldKit.properties.router | Required. Matches a task to the right playbook. Needs a description. |
| Kit tile: Playbooks | $defs/fieldKit.properties.playbooks | Required, minItems 1. Each playbook needs a name and steps. |
| Kit tile: Roles | $defs/fieldKit.properties.roles | Required, all four: coordinator, generator, verifier, judge. Author is never verifier. |
| Kit tile: Capability map | $defs/fieldKit.properties.capabilityMap | Required, minItems 1. Each area names its routes, requirements, checks, and known limits. |
| Kit tile: Lever | $defs/fieldKit.properties.lever | Required. A tool or API the agent can actually drive, not just prose. |
| Kit tile: End-to-end check | $defs/fieldKit.properties.endToEndCheck | Required. Steps a human would take on the real artifact, plus what passing looks like. |
| Graph decision box | $defs/graph.properties.decision | Required. mode is "loop" or "graph", and the reason is written in the file. |
| Graph node | $defs/unit | Required: name, output, owner, check, passes. No output file means not a unit. |
| Solid arrow | $defs/unit.properties.dependsOn | Empty means parallel. Two or more entries makes the unit a join. |
| Dashed arrow | $defs/graph.properties.handoffs | Optional. A transfer of control between agents, pattern "manager" or "handoff". Not a dependency. |
| Loop limits | $defs/graph.properties.limits | Optional. fixCyclesMax defaults to 5, distinctApproachesBeforeDeadEnd defaults to 3. |
| passes pill | $defs/unit.properties.passes | Boolean. Starts false for every unit. Done means every unit passes. |
Research briefs and evidence synthesis. Pilot, single supervised run, not field coverage.
workspace/handover-v1/kits/research-brief/Relentless fix loop for any Handover run: classify failure, distinct approach ladder, loop budget, fresh verifier each cycle. Proof passed Nov 5, 2026.
workspace/orchestrator/handover-2026-11-05-persistent/kit/Graph from a simple directive: router, units and links, split and join, loop per node. Proof passed Nov 5, 2026, judge PASS.
workspace/orchestrator/handover-2026-11-05-graph-v3/kit/In schema terms, each entry above is a fieldKit with a name, a field, a proofStatus, and a path. Older kits are added when they are next reused, not backfilled by guessing.