Treeship
Reference

Feature matrix

Every shipped Treeship capability, with status, CLI surface, and docs. Generated from feature-inventory.yml.

This page is the canonical list of what Treeship actually ships today. If a capability is described in a blog post or a CHANGELOG entry but does not appear here, treat it as not present.

Source of truth

This page is generated from docs/feature-inventory.yml on every build — edit the YAML, never this file. A linter at scripts/check-feature-inventory.py validates every entry against the codebase (CLI commands, doc paths, test paths exist), and CI fails if this page and the YAML disagree.

Status taxonomy

StatusMeaning
stableShipped, documented, tested. No known gaps. Safe to depend on.
betaShipped and used in practice. Rough edges or thin docs.
experimentalShipped behind a build flag or with explicit caveats. May change.
quarantinedShipped code found unsound; fails closed and is non-authoritative. Kept as a marker, not a feature.
roadmapDesigned or specced. Not implemented. Listed here so you know it is on the radar.
deprecatedStill supported, but discouraged. A replacement exists.

Pick stable only when the code, docs, and tests all line up. If the docs page is missing, the right status is beta, not stable.

Core protocol

FeatureStatusCLIDocs
Receipts (signed artifacts)stabletreeship attest action, treeship wrap, treeship logArtifacts
Session reportsstabletreeship session start, treeship session close, treeship session reportSession Receipts, session
Session packages (.treeship bundles)stabletreeship package inspect, treeship package verify, treeship bundle export, treeship bundle importpackage, bundle
Offline verifier (Rust CLI)stabletreeship verify, treeship package verify, treeship merkle verifyverify, Verification surfaces
WASM verifier (@treeship/verify)stable--@treeship/verify, Verifying receipts on the edge
Merkle checkpointsstabletreeship checkpoint, treeship merkle proof, treeship merkle status, treeship merkle publishMerkle proofs, merkle
Merkle consistency proofs (append-only evidence)stabletreeship merkle publishMerkle consistency proofs
Hub-checkpoint consumer verifierstable--Merkle Checkpoints
Hub transport (attach, push, pull, DPoP)stabletreeship hub attach, treeship hub push, treeship hub pull, treeship hub statusHub API Overview, hub
Trust roots (split kinds)stabletreeship trust list, treeship trust add, treeship trust remove, treeship keys exporttrust, Trust model

Identity, approval, attribution

FeatureStatusCLIDocs
Approval Use Journalstabletreeship approval uses, treeship approval status, treeship approval journal verifyApproval Use Journal, Approval Authority
Per-agent keys & onboardingstabletreeship onboard, treeship agent registerTrust model, How it works
Agent Identity Certificatesbetatreeship agent registerAgent Identity
Agent Cardsstabletreeship agents, treeship agents review, treeship agents approve, treeship agents removeAgent Cards, agents
Capability cards & provenance gradesstabletreeship attest card, treeship verify-capability, treeship revoke-capabilityCapability Cards
Harness Managerstabletreeship harness list, treeship harness inspect, treeship harness smokeAgent Harnesses, harness
Multi-agent session invitationsbetatreeship session invite, treeship session join, treeship session countersignMulti-Agent Sessions

Provenance & discovery

FeatureStatusCLIDocs
Agent resolver (local + network)stabletreeship resolve, treeship publishresolve, Agent Resolution
Transparency log & auditstabletreeship auditaudit, Agent registry endpoints
Work history (session.v1 records)betatreeship historyhistory
Recomputable agent profilesbetatreeship profile, treeship verify-profileprofile / verify-profile
Evidence-based agent matchingbetatreeship matchmatch
Presentations & challenge handshakebetatreeship present, treeship verify-presentationpresent / verify-presentation, The Agent Handshake
Selective capability disclosurebetatreeship presentpresent / verify-presentation
Portable receipt export + reference verifierstabletreeship receipt exportreceipt export

Capture surfaces

FeatureStatusCLIDocs
Background daemonbetatreeship daemon start, treeship daemon stop, treeship daemon statusdaemon
OpenTelemetry bridgeexperimentaltreeship otel test, treeship otel status, treeship otel exportotel
MCP stdio server (@treeship/mcp)stable--@treeship/mcp, @treeship/mcp
A2A bridge (@treeship/a2a)beta--@treeship/a2a

Supply chain

FeatureStatusCLIDocs
npm binary SHA-256 integrity checkstable----

Agent integrations

FeatureStatusCLIDocs
Integration -- Claude Codestable--Claude Code
Integration -- Cursorstable--Cursor
Integration -- Codexstable--Codex
Integration -- OpenClawbeta--OpenClaw
Integration -- Hermesbeta--Hermes
Integration -- generic MCP clientstable--@treeship/mcp
Universal Treeship SKILL.mdstable--Agent Skills

Zero-knowledge proofs

FeatureStatusCLIDocs
ZK -- Circom Groth16 (snarkjs shell-out)quarantinedtreeship prove, treeship verify-proof, treeship zk-setupZero-knowledge proofs
ZK -- RISC Zero local prover (prove-chain)experimentaltreeship prove-chainZero-knowledge proofs
ZK -- Circom native pure-Rust (ark-circom)roadmap----
ZK -- RISC Zero Bonsai (hosted proving)roadmap----
ZK -- TLSNotary (verifiable TLS evidence)roadmaptreeship zk-tls-setup--

Both zk CLI paths require the --features zk build flag; the zk feature is pre-release and nothing in the default trust path depends on it.

How to update this page

  1. Edit docs/feature-inventory.yml (add section: so the entry lands in the right table).
  2. Run python3 scripts/check-feature-inventory.py --strict — fix any warnings about your own entries.
  3. npm run sync:feature-matrix in docs/ (or just build — prebuild regenerates it).
  4. If you are adding a new feature, surface it in the next CHANGELOG entry too.