What the redacted Stash cloud receipt observed, how it is correlated, and where its proof boundary ends.
The repository contains a redacted, machine-validated production receipt generated at 2026-08-17T18:38:41.216Z. It records one correlated observation run across CockroachDB Cloud and the deployed AWS stack.
Open the raw receipt
Inspect the redacted JSON used by the production audit.
The evidence composer accepted every required correlation and set the result to true.
stack
CloudFormation reported stack stash-production in UPDATE_COMPLETE.
smoke.health
The deployed API returned an ok health receipt and request ID.
smoke.workspace
Repeating the same bootstrap produced the same tenant and principal identities, demonstrating idempotent workspace creation for that run.
smoke.bedrock.evaluator
Bedrock returned a provider request ID for the configured evaluator model.
smoke.bedrock.embedding
Bedrock returned a provider request ID, 1024 dimensions, and a content digest for the embedding probe.
smoke.s3
S3 returned a provider request ID, version ID, key, digest, and ETag for the content-addressed evidence artifact.
smoke.eventBridge
EventBridge returned a provider request ID and event ID.
vector.vector
CockroachDB reported VECTOR(1024), index memory_versions_active_embedding_idx, ready and visible state, a succeeded job, and an EXPLAIN plan naming the index.
ccloud.ccloud
CockroachDB Cloud tooling reported the expected cluster identity, AWS provider, us-east-1 region, Basic tier, host, and CREATED state.
cloudWatch, xray, serviceEventId
Correlated service observations recorded the run through logs, trace identity, and lifecycle event delivery.
The smoke, vector, and ccloud sections share the same run ID and cloud-resource context. The composer rejects mismatched runs, cluster identities, regions, artifacts, model metadata, or missing observations.
This is point-in-time evidence. It does not certify continuous uptime, future configuration, absence of every vulnerability, or correctness for inputs outside the observed run.
The receipt also does not replace per-release evaluation artifacts and audit events. Those establish why a specific memory candidate was approved and promoted.
Run the evidence commands from an authenticated environment with access to the expected AWS account and CockroachDB cluster:
npm run evidence:contextnpm run aws:smokenpm run vector:evidencenpm run ccloud:evidencenpm run cloud:evidencenpm run production:audit
The scripts fail closed on missing providers, wrong identity, stale correlation, an unready vector index, mismatched artifact digest, or malformed output. Publish only the redacted result.