Summary & Motivation
To guarantee that letitloop remains mathematically indestructible against rogue workers, file system corruptions, and flaky external commands, we want to build a formal Adversarial Fault Injection & Mutation Testing Suite.
Proposed Fault Injection Scenarios
- Out-of-Bounds File Mutation:
- A mock worker attempts to modify files in parent directories (
../../etc/passwd or ../sibling_module). Verifies scope.py blocks/detects the violation 100% of the time.
- Zombie Process Leakage:
- A mock worker forks child background processes that refuse
SIGTERM. Verifies supervisor cleans them up.
- Simulated State Journal Corruption:
- Injects truncated JSON or random byte noise into
journal.jsonl mid-turn. Verifies apply_checkpoint and WAL recovery reconstruct valid state without crashing.
- Deterministic Infinite Loop Simulation:
- A mock worker produces identical non-divergent outputs across retries. Verifies
failure.py 3-strike impossibility triggers deterministically on Strike 3.
Acceptance Criteria
Summary & Motivation
To guarantee that
letitloopremains mathematically indestructible against rogue workers, file system corruptions, and flaky external commands, we want to build a formal Adversarial Fault Injection & Mutation Testing Suite.Proposed Fault Injection Scenarios
../../etc/passwdor../sibling_module). Verifiesscope.pyblocks/detects the violation 100% of the time.SIGTERM. Verifies supervisor cleans them up.journal.jsonlmid-turn. Verifiesapply_checkpointand WAL recovery reconstruct valid state without crashing.failure.py3-strike impossibility triggers deterministically on Strike 3.Acceptance Criteria