Reproducible source evidence

This page is generated by bun run evidence:sync. Its inputs are copied from the Stacks repository and verified byte-for-byte against evidence/stacks/evidence.lock.json. It reports inventory, not quality or conformance.

Evidence	Immutable revision
Evidence-producing Stacks commit	`2a17dd38ffbe9f910273e3777079e7f1ec1623ba`
Audited Stacks source tree	`bf1245e336ab14551e22cb7d88284f93e649a1a2`
RFC repository	`ea9dbe438aca308085372e68aaa82ebe2e92b8d0`
Source digest	`sha256:2d2f35689576a8d546acd5f13c69029aeb6609bca7506b953271d8f03c82ee8e`

The source manifest classifies Stacks as a reference implementation with an unverified protocol claim. No package count or unit test upgrades that claim.

Package provenance

Package	Version	Manifest path
`@stacksjs/config`	`0.70.161`	`storage/framework/core/config/package.json`
`@stacksjs/desktop`	`0.70.161`	`storage/framework/core/desktop/package.json`
`@stacksjs/env`	`0.70.161`	`storage/framework/core/env/package.json`
`stacks`	`0.70.52`	`package.json`
`stacks`	`0.70.161`	`storage/framework/core/package.json`

The root workspace and published framework package intentionally remain separate rows. Consumers must identify an exact source revision and package manifest rather than treating one repository-wide version string as authoritative.

Classified inventory

Category	Files	Bytes
assets-and-data	805	12,072,026
configuration	248	688,648
documentation	477	4,047,580
generated	27	169,642
source	2,026	8,458,161
tests	464	2,660,743
vendored-protocol	13	74,212

Total: 4,060 files and 28,171,012 bytes across 90 versioned package manifests. Generated, test, docs, configuration, vendored protocol, and source files are deliberately separate.

Driver evidence

The runtime-linked registry contains 27 individual records across database, queue, cache, storage, mail, realtime, and deployment.

Status	Drivers
supported	11
partial	9
experimental	3
unsupported	4

“Supported” requires checked-in automated evidence. “Partial” lacks live-service or parity evidence, “experimental” lacks a compatibility commitment or complete matrix, and “unsupported” must fail loudly. Service versions and CI-run URLs belong in per-run conformance reports rather than this static inventory.

Environment encryption

The pinned source writes the experimental encrypted:v2 envelope proposed in RFC 0005: ephemeral-static X25519, HKDF-SHA-256, and AES-256-GCM with authenticated metadata. The legacy format is read only for migration. Broad production recommendation remains blocked on RFC ratification and independent review.

Craft desktop evidence

The generated Craft matrix has 0 stable targets. macOS arm64/x64, Linux x64, and Windows x64 are experimental unpackaged bundles; unlisted targets are unsupported. Stable publication is mechanically blocked until platform signing/notarization and retained native install, launch, update, rollback, and uninstall evidence exist. See #2059, #2062, and #2063.

Refresh procedure

Check out the intended Stacks revision with its dependencies available.
In Stacks, run all protocol evidence checks and intentionally refresh the source manifest for the selected immutable revision.
In this repository, run bun run evidence:sync -- --source ../stacks.
Review the lock, generated page, capability changes, and limitation changes.
Run bun run evidence:check and bun run build before committing.