open protocol for agent work

Proof across session boundaries.

Baton is a lightweight protocol for AI-assisted engineering: plan the work, implement one slice, write proof from live repo state, then verify in a fresh context that never saw the implementer's framing.

Read the protocol View schema

{
  "$schema": "https://baton.sawy3r.net/schemas/slice-status-v1.json",
  "slice_id": "S03-account-settings",
  "state": "implemented",
  "test_commands": ["pnpm test account-settings"],
  "reachability_artifacts": ["e2e/account-settings.spec.ts"],
  "verification": {
    "result": "pending",
    "verifier_was_fresh_context": null,
    "violations": []
  }
}

planned -> in_progress -> implemented
                         -> verified | failed

The baton is the proof bundle.

Baton turns agent work into durable artefacts instead of transcript folklore. The handoff between roles is a file on disk: spec, status, proof. The verifier reads those artefacts in a sealed context and fails closed unless the evidence is complete.

Reach the product path

Feature proof starts at the integration point that owns the user-facing affordance, not an isolated leaf.

Write proof from repo state

Completion claims require files changed, test output, reachability artefacts, and explicit non-delivery.

Verify fresh or fail closed

The verifier starts with no inherited transcript and returns only PASS, FAIL, or BLOCKED.

Canonical schema home.

Baton artefacts use resolvable schema URLs. This site hosts the public contract while the source of truth remains the open protocol repo.

slice-status-v1.json schema release-mode templates github protocol README github