DR original Release Management artifact exercise,2026-10-04

python3 content/labs/release-artifacts/run.py --output /tmp/dr-release-artifacts.json
Choose a new output path. Python standard library, private temporary files only.
Recorded CPython3.13.1 on Darwin arm64. Rolling Python3.13 docs label3.13.16;
this does not replace the executed runtime. No network or downloaded software.

Twelve groups passed twice. Require exit0, passed12, failed0, failure null and
matching scriptSha256. The two original files are app.py and dependency.py.
Changing ZIP timestamps or member ordering changes archive bytes despite identical
member hashes. Normalized names, dates, Unix metadata and ZIP_STORED produce
identical bytes in two local builds. This is not cross-toolchain reproducibility.
Two subprocesses execute only known original input files, never archive contents.
The same app.py returns20 with SCALE2 and30 with SCALE3 in the original dependency.

A partial manifest misses runtime.json. The stricter fixture rule checks exact
member names, duplicate names, a per-member size bound and member hashes. It rejects
additional names, duplicate app.py and ../outside.txt without extracting anything.
This is not a general secure archive validator. No attack on any external system.
A replacement manifest matching a replacement package passes internal consistency,
but the retained original expectation rejects it. No signature, trusted builder,
SLSA verifier or human approval is implemented or implied.

The source passes an initial hash check, is deliberately substituted, and is then
copied. Checking incoming rejects the changed bytes and preserves promoted.zip.
This is controlled sequential substitution, not an executed concurrent race.
The next correct copy passes checks and replaces the destination locally with
os.replace. Same-filesystem replacement is not a distributed transaction, crash
recovery or runtime acceptance. No general protection against writers between
checking and use is implemented. The private fixture has no such competing writer.
Payload equality alone does not transfer approval bound to the entire archive.

All temporary files are removed and the two owned subprocesses complete. No
received ZIP is extracted or executed. No third-party package, registry, signing,
production promotion, malicious-input hardening, benchmark, payment, power failure
or human workshop. Original examples do not represent procedures of financial institutions.
Representative build/provenance/access/runtime acceptance and independent review
remain outstanding. Local quantities and checks do not establish course maturity.
