DR original Release Management HTTP routing exercise,2026-10-04

Run from project root:
python3 content/labs/release-routing/run.py --output /tmp/dr-release-routing.json
Choose a new output path. Requires permission for local loopback sockets only.
CPython3.13.1 on Darwin arm64 was recorded. Python3.13 rolling documentation
currently labels3.13.16; this does not change the executed interpreter version.

Thirteen groups passed twice with identical checks and completion-order trace.
Require exit0, passed13, failed0, failure null, and matching scriptSha256.
Three owned listeners bind127.0.0.1 on system-assigned ports, in one process using
request threads. HTTP client proxy discovery is explicitly disabled. No external
endpoint is accessed. The script owns only its sockets, threads and temporary tree.

blue returns100. green is directly ready but receives no router traffic initially.
Enabling candidate routes only the supplied pilot cohort to green; control remains
blue. This is deterministic selection, not random sampling, a percentage or an
authenticated identity. green passes ordinary but deliberately returns108 for
critical, violating the required100 despite HTTP200. No export request is observed:
its rate is unknown, not zero. No capacity or statistical confidence is measured.

An actual pilot POST enters green and waits on an Event before writing. Only after
confirmed admission does policy return to blue. A new pilot POST writes blue/100
while the old request remains pending. Releasing the Event allows green/108 to be
written afterward. The trace records responses on completion, not admission order.
Routing does not retroactively cancel or reroute the admitted request. The receipt
contains blue/100 then green/108. Candidate shutdown happens after that completion;
subsequent traffic returns blue/100 and the receipt remains unchanged. No payment,
reconciliation or compensation is performed. The values are original arbitrary
fixtures, not financial formulae. The script has no retry or idempotency mechanism.
Connection-loss discussion is an additional unexecuted scenario.

All owned sockets close, server/client threads terminate and temporary files are
removed, including the bounded failure-cleanup path. No existing service is stopped.
http.server is not recommended for production. This is not a production proxy.
No enterprise load balancer, cluster, Kubernetes, DNS, TLS, authentication, external
pipeline, real production rollout, persistent-session test, multiplexing, client
cancellation, network failure, power loss or benchmark. Target routing, work draining,
retry contracts, compatibility and operational acceptance remain to be exercised.
The proposed human workshop has not been performed; independent review remains.
