Path traversal blocked • Strict probe allowlist • Zero token leaks
Project & Failure Scenario Workspace
Scenario A
Container crashes with KeyError: DATABASE_URL. Engine confirms missing variable without leaking secrets, proposes compose patch, and verifies in sandbox.
Scenario B
Logs appear normal, but container is unhealthy. Compose probes /health while app routes /healthz. Requires active diagnostic probe to pinpoint mismatch.
Scenario C
Compose forwards host 8000 to container 5000, but app listens on 8000. Engine verifies listening ports with TCP probes and generates aligned port patch.
Scenario D
External gateway connection resets intermittently. Engine exhausts local probes, refuses to hallucinate a fake patch, and reports insufficient_evidence honestly.
Scenario E
Application logs show database timeouts, but container inspect reveals OOMKilled: true (exit 137). Engine identifies kernel memory exhaustion.
Scenario F
Logs report Redis connection error, but compose config explicitly sets REDIS_ENABLED=false. Engine detects contradiction and avoids unnecessary patch.
Scenario G
App failed startup due to invalid rate limit configuration. An adversarial patch with syntax regression is caught by sandbox and reverted.
No Investigations Recorded Yet
Select a scenario above and click "Start Investigation" or "3-Min Judge Demo" to begin an evidence-driven diagnostic cycle.