One Fault Cohort: Execution, Evidence, and Cleanup

One Fault Cohort: Execution, Evidence, and Cleanup A workflow diagram generated by Archify. 01 / Cohort · Evidence · Bounded Cleanup EX / Timeout / Cancellation Predeclare Exercise the boundary Assess + preserve Seed + Plan · IDs + checks · Cohort · Evidence · Bounded Cleanup › Predeclare Seed + Plan IDs + checks Workers · bounded · Cohort · Evidence · Bounded Cleanup › Predeclare Workers bounded Fault Gate · real socket · Cohort · Evidence · Bounded Cleanup › Exercise the boundary Fault Gate real socket Outcome · public API · Cohort · Evidence · Bounded Cleanup › Exercise the boundary Outcome public API Evidence · two-sided · Cohort · Evidence · Bounded Cleanup › Assess + preserve Evidence two-sided Report · after close · Cohort · Evidence · Bounded Cleanup › Assess + preserve · all checks Report after close all checks Partial Report · bounded cleanup · Timeout / Cancellation › Assess + preserve · incomplete ≠ pass Partial Report bounded cleanup incomplete ≠ pass inject dispatch + commit checks timeout / cancel

Verified Contract and Sources · acb7fa96d

  • • Seeded assignments and bounded workers: scripts/stress_fault_server.py
  • • Evidence contract: tests/_fault_server/common.py · docs/fault-injection.md
  • • Real socket gates and independent dispatch/commit evidence: tests/_fault_server/web_scenarios.py · tests/_fault_server/http.py
  • • Cleanup is bounded and secondary errors preserve the primary failure; recovery is checked only where defined; incomplete evidence cannot pass