Treeship
Reference

Feature matrix

Every shipped Treeship capability, with status, CLI surface, and docs.

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

The hand-maintained source is docs/feature-inventory.yml in the repo. A small linter at scripts/check-feature-inventory.py walks every entry and warns when a listed CLI command, docs page, test file, or package manifest cannot be found. The linter does not fail builds today; that is a deliberate later step once the inventory has burned in.

This MDX page is hand-maintained from the YAML. Auto-generation from YAML at build time is on the roadmap but intentionally not in the bootstrap PR. If you change one, change the other.

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.
roadmapDesigned or specced. Not implemented. Listed here so you know it is on the radar.
internalExists in code but is not a user-facing feature. Supports something else.
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 / close / reportSession receipts
Session packages (.treeship bundles)stabletreeship package inspect / verify, treeship bundle export / importPackage CLI
Offline verifier (Rust CLI)stabletreeship verify, treeship package verify, treeship merkle verifyVerify CLI
WASM verifier (@treeship/verify)stable--Verify SDK, Edge runtime guide
Merkle checkpointsstabletreeship checkpoint, treeship merkle proof / status / publishMerkle proofs
Hub-checkpoint consumer verifierstable--Merkle checkpoint API
Trust rootsbetatreeship trust list / add / removecovered inline in security notes; no dedicated page yet

Identity, approval, attribution

FeatureStatusCLIDocs
Approval Use Journalstabletreeship approval uses / status, treeship approval journal verifyApproval Use Journal
Agent Identity Certificatesbetatreeship agent registerAgent identity
Agent Cardsstabletreeship agents, agents review / approve / removeAgent Cards
Harness Managerstabletreeship harness list / inspect / smokeHarnesses

Capture surfaces

FeatureStatusCLIDocs
Background daemonbetatreeship daemon start / stop / statusDaemon CLI
OpenTelemetry bridgeexperimentaltreeship otel test / status / export (behind --features otel)OTel CLI
MCP stdio server (@treeship/mcp)stable--MCP integration, MCP SDK
A2A bridge (@treeship/a2a)beta--A2A integration

Supply chain

FeatureStatusCLIDocs
npm binary SHA-256 integrity checkstable-- (runs at npm install)covered in Install guide

Agent integrations

FeatureStatusCLIDocs
Claude Codestabletreeship addClaude Code
Cursorstabletreeship addCursor
Codexstabletreeship addCodex
OpenClawbetatreeship addOpenClaw
Hermesbetatreeship addHermes
Generic MCP clientstable--MCP integration
Universal Treeship SKILL.mdstable--Agent skills

Kimi Code CLI consumes the universal SKILL.md but is not a detected surface in treeship add --discover. Tracked under the agent-skills entry.

Zero-knowledge proofs

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

Both zk CLI paths require the --features zk build flag. The Bonsai path is gated on a v0.6.x milestone per packages/zk-risc0/src/prover.rs; the README is explicit that TLSNotary is waiting on the upstream alpha to stabilize.

How to update this page

  1. Edit docs/feature-inventory.yml.
  2. Run python3 scripts/check-feature-inventory.py -- fix any warnings about your own entries.
  3. Mirror the change in this MDX file. (Auto-generation from YAML is roadmap.)
  4. If you are adding a new feature, surface it in the next CHANGELOG entry too.