Night Shift / D6 · Work-order response lost after commit

D6 · Work-order response lost after commit

The same lost-response shape as D5, on the facilities effect. Instrumented across seeds, a scripted run makes 143 commit_effect calls, exactly one create_work_order call, and replays zero receipts. Nothing retries after the loss, so what this drill establishes is that the lost response leaves one work order behind. The retry path stays unexercised on the scripted tier.

idempotencyAll drills

Expectations

Properties of the outcome, not scenario identifiers

all_invariants_hold
Every hard invariant N1-N13 holds in the final snapshot
no_duplicate_effect
No semantic action produced more than one committed effect
fault_actually_fired
The injected fault fired
one_work_order_per_fault_class
At most one work order per fault class

Injected faults

Keyed on (tool, action id, call number) so a rerun reproduces exactly

Tool	Call	Kind
create_work_order	1	commits, response lost

Runs

6 recorded run(s) across the campaign

#	Driver	Seed	Result	Final state	Faults	Tool calls	Reconciled	Unmet	Time
6	scripted	20260826	PASS	CLOSED	1	105	42/42	—	0.46s
27	scripted	20260927	PASS	CLOSED	1	105	42/42	—	0.57s
48	scripted	20261028	PASS	CLOSED	1	105	42/42	—	0.68s
69	scripted	20261129	PASS	CLOSED	1	105	42/42	—	0.73s
90	scripted	20261230	PASS	CLOSED	1	105	42/42	—	0.76s
111	scripted	20261331	PASS	CLOSED	1	105	42/42	—	0.92s