CONCEPT Cited by 5 sources
Reproducible builds¶
Definition¶
A reproducible build compiles the same source into a byte-identical artifact every time, regardless of who runs the build or where. That turns a binary's hash into a property of its source: anyone can rebuild from public source, get the same digest, and thereby link a running or published binary back to code they can audit. Achieving it requires eliminating non-determinism — timestamps, file ordering, absolute paths, toolchain versions, embedded build IDs — usually via pinned, hermetic toolchains.
Why it matters for system design¶
Remote attestation proves which digest is running in a TEE; it says nothing about what that digest does. Reproducible builds close the gap: the attested measurement can be recomputed from audited source by an independent party, so attestation + reproducibility together give "this audited source is what's executing." A second-order benefit: since the measurement is deterministic, verifiers can pin constant expected values (e.g. Nitro PCRs) — "verification policies never need to be updated" across rebuilds (Source: sources/2026-10-27-aws-how-anchorage-digital-and-turnkey-verify-code-with-aws-nitro-enclaves). It is also the precondition for a meaningful binary transparency log: a published digest is only auditable if it can be regenerated from source.
Seen in¶
- sources/2026-10-29-zalando-upgrading-mlflow-pipelines-across-a-python-version-boundary
— weaker ML-artifact form: reproducible environments, not byte-identical
binaries. Zalando pins packages and lets MLflow (≥ 3.11.1) export exact
requirements from
uv.lockat log time, so each model artifact declares the environment that can load it. - sources/2026-10-27-aws-how-anchorage-digital-and-turnkey-verify-code-with-aws-nitro-enclaves — VisualSign + QuorumOS images are reproducibly built so wallets compare Nitro Enclave PCRs against build-derived values; any party can verify the enclave runs the exact unmodified parser.
- sources/2026-10-02-google-toward-provably-private-learning-from-federated-data — KMS and data-processing binaries in systems/confidential-federated-compute are reproducibly built from open source, so attested measurements in the key-release policy map back to auditable code.
- sources/2025-10-30-google-toward-provably-private-insights-into-ai-use — pre-approved, attested, reproducibly-buildable processing steps in Google's confidential federated analytics, with digests on a public transparency log.
- sources/2026-09-29-cloudflare-building-a-certificate-authority-for-the-whole-internet — systems/cloudflare-certificate-authority commits to reproducible builds of its signing software (plus attested HSMs) as a CA transparency measure between audits.
Related¶
- concepts/remote-attestation — the runtime proof reproducibility makes meaningful.
- concepts/trusted-execution-environment · concepts/confidential-computing
- patterns/attestation-gated-key-release — key-release policies keyed on reproducible measurements.