Treeship
Reference

Protocol specs index

Every design spec in docs/specs/, with its real implementation status — frontiers get a spec before code, and this index says which frontiers have been reached.

Treeship's rule is spec before code: each protocol surface gets a design document in docs/specs/ before implementation. Specs ship in slices, so a spec being "done" is rarely binary — this index gives the honest status of each one as of v0.20, sourced from the CHANGELOG.

The Status: headers inside some spec files lag behind the shipped product (several still say "not implemented" for features that shipped releases ago). Until status is generated from the feature inventory, trust this index and the changelog over the file headers.

Shipped

SpecStatusShipped as
per-actor-signingShippedPer-agent keys + agent_cert.v1 (v0.13); MCP/A2A bridges auto-provision keys (v0.15+) — the proven (key-bound) grade
agent-capability-cardsShippedattest card, verify-capability, revoke-capability (v0.13); WASM verifyCapability
agent-resolverShippedLocal resolve (v0.13), network resolve --hub + publish (v0.14)
transparency-logShippedMerkle anchoring + audit (v0.14), witnessing + equivocation detection (v0.15)
merkle-consistencyShippedConsistency proofs + append-only audit chain (v0.15)
commitmentsDraftProving what an agent promised vs what it did. Slices 1-4 unbuilt; two adjacent ideas shipped separately (AuthorityUse #297, objective binding #298)
time-anchoringDraft, not implementedReceipt timestamps are self-asserted (SystemTime::now(), signed by the agent's own key). Specifies external witnessing so when is provable, not just what
capability-provenanceShippedThe captured / exercised / discovered / declared grade system across cards, resolve, and verify-capability
work-historyShipped (slices 1–4)session.v1 records (v0.16), history, profile / verify-profile, match (v0.18)
protocol-integrationShipped (slices 1–3)MCP per-agent key provisioning, --tools-json, --from-a2a + A2A provable receipts
registry-topologyShipped in behaviorPresentations, Merkle staples, challenge handshake (v0.17); the doc doubles as topology analysis
agent-invitations-roomsShipped (phase 1)session invite / join / countersign, session_host trust kind; countersigning hardened in v0.19

Partial or design-stage

SpecStatusNotes
private-verificationPartialSelective capability disclosure shipped in v0.20 (present --disclose); the statement-first ZK tiers remain design (the prior Groth16 path is quarantined)
memory-provenance-bindingDesignThe why-believed axis: memory provider ledger contract (zmem.sh), quarantine-gated approvals, chain-root commitment, effect-status ladder. Marks SHIPPED vs NEW per section; phases 1–2 run on today's primitives
receipt-systemDraftOne signed data model rendered for three audiences, agent-first; the honesty gradient is machine-readable, not prose. Builds on the shipped action/v2 mandate + effect
trusted-roomsDraftProduct spec building on invitations/rooms
token-captureDraftWorking notes
local-dashboardDraftA dashboard ships behind a hidden command; the spec is ahead of it
workflow-declarationsSlices 1-2 + slice-3 primitivesGolden reports, pure reducer, registered/signed workflow.v1, real checkpoint pre-existence verification, and signed first-run binding via session start --workflow-ref. Automatic checkpoint composition and CLI conformance verification remain
cyberlogic-trust-modelTheory, first draftA first-principles account of Treeship's trust model
visionLiving documentThe roadmap source of truth
agent-to-agent-verificationSlices 1–4 shipped (0.27.0); 3b blockedThe default-on gate ships in @treeship/a2a and @treeship/mcp (refuse foreign work until verify-presentation --challenge passes; refusals and opt-out skips are signed), every harness skill teaches it, attest handoff --verified records the verify as custody: live and verify grades it, and --close-loop binds sealed-session evidence. Grok approvals (3b) are blocked: nothing on the VM exposes the decision
grok-bot-a2aImplemented (slices 1–4); 3b blockedReference host: bootstrap, shim, packaged skill, routine, and the treeship.a2a/v1 envelope ship under integrations/grok-bot/. Runtime facts verified against docs.x.ai 2026-09-01; the two-ship handshake is proven on real ships in CI, not yet on a Grok Bot VM
grok-bot-h2aImplemented via the A2A gate; 3b blockedHarness note under agent-to-agent-verification: the two human verbs ("prove you", "receipt this") are the same handshake with a person minting the nonce. Slice 3b (receipt the approvals) is blocked: Grok exposes approval decisions only in its app UI