---
title: tapes-crates
description: The tapes-crates reference.
editUrl: https://github.com/papercomputeco/tapes-crates/tree/main/docs
sourceRepo: papercomputeco/tapes-crates
sourcePath: docs/
lastUpdated: 2026-08-14
---

Reference pages for tapes-crates, synced at build time from
[papercomputeco/tapes-crates](https://github.com/papercomputeco/tapes-crates). Each page is owned by
that repo, so a behavior change and its documentation land in the same
pull request there.

- [tapes-crates](/docs/tapes-crates/introduction/) — The client-side Rust crates for tapes — the crate map, the boundary each crate owns, and how to take them from crates.io.
- [tapes-capture](/docs/tapes-crates/tapes-capture/) — The capture protocol crate — the X-Tapes-* envelope and its budgets, the gateway environment contract with its two sub-protocols, and the peer-trust primitives.
- [tapes-harnesses](/docs/tapes-crates/tapes-harnesses/) — The harness-knowledge crate — the registry and its five axes, the three capture mechanisms, launch recipes, plugin artifacts, attribution lanes, and transcript discovery.
- [tapes-client](/docs/tapes-crates/tapes-client/) — The read client — one core contract sealed at build time, a deployment's cassettes discovered at start, one transport seam, and a credential hook instead of a transport.
- [Adding a harness](/docs/tapes-crates/adding-a-harness/) — Teaching the crates about a new coding agent — the registry declaration, the launch recipe decision, the bar a new attribution lane must clear, and what breaks when the registry changes.
- [The harness regression matrix](/docs/tapes-crates/harness-matrix/) — The CI tier that launches each real harness binary through a mock provider and a mock ingest, and asserts on what actually crossed the wire.
- [Releasing](/docs/tapes-crates/releasing/) — How the three crates reach crates.io — dependency order, the tag scheme, what the release workflow checks, and the two-lock hold on the upload.