v0.1.0 — the assurance spine (Alpha)

The first capability release: the assurance spine, simulation-only. A validated Alpha entering community evaluation — not a finished production platform. Not on PyPI yet; that follows community evaluation.

• Canonical traces — versioned digests (c1:sha256:…) byte-identical across machines, plus a rolling event chain.
• Invariant contracts — never / eventually / every / precedes over the event stream; verdicts live outside the trace.
• Proof bundles — evarness prove runs each scenario twice, checks reproduction and contracts, records a mandatory not_proven scope; tri-state verdict (HOLDS / PENDING / FAILED).
• Offline verification — evarness verify recomputes digests, chains, and verdict consistency from the bundle alone; optional Ed25519 signing.
• The agents domain — thirty-one node types with packaged patterns and deterministic simulation; real providers and tools refuse with actionable errors.
• Render artifacts, proof browser, interchange export, extension seams — see CHANGELOG.md and the decision log.

The receipts

Two proof bundles generated by this release's code from the shipped approval_gated_send pattern, attached below:

bundle	verdict	headline digest
proof-approval_gated_send-pending.json	PENDING (paused at the human gate — nothing evaluated, honestly)	c1:sha256:8c4b5f50a76a9ca232972a5c4cbadb6ca52b5cbf468d4bdc1d53a23cb1c422a0
proof-approval_gated_send-approved.json	HOLDS (3 invariants, reproduction demonstrated)	c1:sha256:60439b6a…

Verify either one offline:

pip install "evarness @ git+https://github.com/evarness-ai/evarness.git@v0.1.0"
evarness verify proof-approval_gated_send-approved.json

Or reproduce the digests yourself:

# Expected: PROOF: PENDING and exit code 1 — the gate is the feature
evarness prove approval_gated_send -o proof.json
evarness prove approval_gated_send --approve n3=approve -o proof.json
evarness verify proof.json