# Stash

> Release control for durable AI-agent memory

## Docs

- [Stash documentation](https://docs.trystash.xyz/index.md): Release control for durable AI-agent memory.
- [Local quickstart](https://docs.trystash.xyz/quickstart.md): Start Stash locally and create an isolated demo workspace.
- [Release your first memory](https://docs.trystash.xyz/tutorials/first-release.md): Guide one memory candidate through screening, evaluation, approval, promotion, retrieval, and rollback.
- [Architecture and trust boundaries](https://docs.trystash.xyz/concepts/architecture.md): How Stash separates its reviewer console, application API, evidence workers, and transactional memory store.
- [Memory release lifecycle](https://docs.trystash.xyz/concepts/release-lifecycle.md): The candidate state machine, evidence gate, promotion protocol, and forward-only rollback model.
- [Why Stash uses CockroachDB](https://docs.trystash.xyz/concepts/why-cockroachdb.md): How transactions, tenant-scoped keys, vector indexing, revisions, and the outbox support governed memory releases.
- [Security and provenance model](https://docs.trystash.xyz/concepts/security-model.md): Identity, tenant membership, reviewer authorization, signed provenance, and fail-closed evidence behavior.
- [How to review a memory change](https://docs.trystash.xyz/guides/review-change.md): Screen, evaluate, and approve or reject a candidate against its exact evidence.
- [How to roll back a memory lineage](https://docs.trystash.xyz/guides/rollback-lineage.md): Restore a prior payload by creating a new forward revision.
- [How to inspect release evidence](https://docs.trystash.xyz/guides/inspect-audit.md): Trace a memory release across request IDs, candidate state, evaluation evidence, and audit lineage.
- [How to deploy the production stack](https://docs.trystash.xyz/guides/deploy-production.md): Migrate CockroachDB, deploy the AWS evidence plane, configure Vercel, and run fail-closed production checks.
- [HTTP interface](https://docs.trystash.xyz/reference/http-api.md): Authentication, headers, validation, routes, and mutation bodies for the Stash v1 service.
- [Configuration](https://docs.trystash.xyz/reference/configuration.md): Runtime, deployment, test, and browser-visible environment variables.
- [Lifecycle states](https://docs.trystash.xyz/reference/lifecycle-states.md): Exact candidate states, events, and valid transitions.
- [Commands](https://docs.trystash.xyz/reference/commands.md): npm commands for development, verification, documentation, infrastructure, evidence, and deployment.
- [Repository map](https://docs.trystash.xyz/reference/repository-map.md): Maintained source directories and their responsibilities.
- [Production evidence](https://docs.trystash.xyz/evidence/production.md): What the redacted Stash cloud receipt observed, how it is correlated, and where its proof boundary ends.
- [Technical differentiation](https://docs.trystash.xyz/evidence/competitive-differentiation.md): Where Stash differs from direct memory writes and retrieval-only memory systems.