Production Graviton5 launch: a10323d

Exact measured source: a10323dede4413fbf295916b8ad12e3dbad7514e. Started on the existing dedicated c9g.4xlarge parent on 2026-09-09 at 21:18:55 UTC, without debug mode, with 12 CPUs and 24 GiB. Production work is 43,768,124 RandomX iterations per segment, seven segments. The prior short-work diagnostic and all artifacts were preserved. No legacy resources were changed.

Two builds, including an independent empty BuildKit builder with --no-cache, produced identical PCR0/PCR1/PCR2 and Docker image IDs. Full EIF hashes differ because the images carry unmeasured build metadata; this is measurement reproducibility, not byte-identical EIF reproducibility. Both EIF CRC checks passed. reproduce.sh records the actual second-build procedure, with deployment-local paths.

The startup log records explicit NSM entropy injection and kernel reseed before TLS/signing key generation, then CPU verification, NSM parent binding, and live authenticated AWS instance evidence. warming-evidence.json contains the signed NSM document, actual TLS peer certificate, fresh nonce and authenticated policy. Normal SDK verification rejects the warming state, and a forwarding request returns 503. No production puzzle or successful production forwarding request has yet been observed. Based on the prior calibration, first publication is estimated near 2026-09-10 22:27 UTC; this timing and the complete production lifecycle remain unverified. The estimated 25.14-hour generation exceeds the 24-hour epoch interval and may produce fail-closed availability gaps.

The parent has no public HTTP ingress or running Cloudflare tunnel; tests used a private SSH forward. Host operational credential-bridge code has a bounded graceful half-close change outside measured source; its preserved source and initial diagnostic failure/retry evidence are documented in the diagnostic evidence directory. No credential values appear in these logs.