DR incident HTTP/SQLite lab, 2026-10-04

Original teaching service, not production software. Uses Python standard
library only. Recorded: CPython 3.13.1, SQLite 3.51.2, Darwin arm64. Rolling
Python 3.13 documentation currently labels a different patch; runtime versions
are retained in each report. No package installation is required.

From the project directory, with permission to bind local loopback:
python3 content/labs/incident-runtime/run.py --output /tmp/dr-incident-observation.json
Choose a new output filename for each run to preserve evidence. The script
binds only 127.0.0.1 on a dynamically allocated port and creates its own
Temporary SQLite directory. It does not read the platform database or user
credentials. All values are synthetic instruction identifiers and color names.
Do not expose this unauthenticated teaching server to other hosts or use it as
a production service. The idempotency key is not authentication/authorization.

Thirteen groups passed twice. Require process exit 0, passed=13, failed=0,
failure=null, and matching scriptSha256. Inspect observations and event stages,
not only the total. Expected: baseline operation succeeds; dependency flag
makes /ready and operation return 503 while /health stays 200; no effect for
the rejected attempt; deliberate connection close AFTER commit gives client
RemoteDisconnected while a stored effect exists; unprotected retry yields two
effects for one intent; protected retry returns the existing effect; changed
payload with the same key gets 409; missing key gets 400; eight concurrent
same-key calls yield one application and seven replays; unknown route gets
404; restored readiness/new operations do not erase previous duplicate effects;
reconciliation counts six effects for five intents, with SQLite integrity ok.
The last group verifies server thread exit, listener release and removal of
the temporary database. No existing server process is stopped.

The two recorded reports preserve the exact implementation hash. Event order
for concurrent requests may differ; compare group outcomes and their scope.
The script’s own /safe and /unsafe routes define its teaching contract. HTTP
method, status or endpoint names alone do not grant equivalent semantics to
another application. SQLite BEGIN IMMEDIATE and key/effect recording in one
local transaction matter to the result. An external effect outside that
transaction needs its own contract, failure tests and reconciliation.

These are actual HTTP requests and SQLite transactions, with a synthetic
readiness flag and intentional connection close after commit. No external
network outage, process crash, distributed consensus, authentication, payment,
enterprise consumer, load benchmark or human coordination exercise is run.
No distributed exactly-once or production-readiness guarantee is established.

Use worksheet.txt for prediction, diagnosis, communication and handover. The
guide has not been performed by a human group. Independent specialist review
and representative application/dependency acceptance remain outstanding.
