Status: 16 of 17 required lanes passed; Task 13.5 remains open.
The retained record is
eve-fault-chaos/2026-09-14.preparation.json.
It binds source commit 0c0dcafdc2fe0e42f33e867b54879a5517e8fd07, 18 exact
source-file hashes, one runtime and trace identity per lane, at least three
non-secret runtime facts per lane, and a digest over the complete record.
Result#
The coordinator injected and recovered provider loss, endpoint loss, malformed stream, PostgreSQL outage, Redis outage, Qdrant outage, MCP outage, browser outage, Blender/DCC outage, network partition, process crash, lease expiry, telemetry blindness, clock skew, disk pressure, and partial artifact. Each passing row asserts the allowed fallback, zero success claims while faulted, zero unsafe effects, zero duplicate recovery effects, trace continuity, and post-recovery correctness.
pnpm exec tsx tools/eve-everywhere/verify-fault-chaos.mts --allow-preparation
passes with 16/17. The same verifier without --allow-preparation rejects the
record because channel-outage was not executed. This negative result is
required: a preparation record cannot become closure evidence.
Sole blocker#
No credentialed Telegram, Slack, Discord, Signal, Twilio, SMTP, or equivalent external channel is provisioned in the authorized local environment. Task 13.5 requires identity, delivery, safety, kill, and recovery proof against a real credentialed external channel. A mock webhook or local mail sink is not a substitute, so the task checkbox remains open.
Resume point#
Do not rerun the 16 passing lanes while their source hashes and runtime
assumptions remain unchanged. Once a real channel is provisioned, add only the
channel-outage observation, rerun the fail-closed verifier in normal mode,
perform the required independent reviews, and then consider checkbox closure.