Failure injection mode

Incident Catalog

Every week ends in a scenario-based Boss Fight. Root cause stays hidden; hints make the current attempt assisted and therefore ineligible for CLEAN PASS.

INCIDENT #NET-01 · WEEK 1 BOSS FIGHT
OPEN

Browser cannot access localhost:8000

Compose startup finishes, but the learner's browser cannot connect to http://localhost:8000. The responsible layer is not disclosed.

0 attempts · 0 clean pass
Solve incident
INCIDENT #DOCKER-API-02 · WEEK 2 BOSS FIGHT
READ ONLY

Portal/API request fails across multiple layers

The Portal cannot complete a create request. Containers exist, but the UI only reports a generic failure. Port, DNS, environment, database, migration, and proxy remain possible until evidence excludes them.

0 attempts · 0 clean pass
Read scenario
INCIDENT #IDENTITY-03 · WEEK 3 BOSS FIGHT
READ ONLY

Login succeeds but protected API returns 403

A demo user completes login and receives a token, yet the protected purchase endpoint returns 403. Do not disable the Backend guard or grant broad roles.

0 attempts · 0 clean pass
Read scenario
INCIDENT #WORKFLOW-04 · WEEK 4 BOSS FIGHT
READ ONLY

Workflow executes twice and creates a duplicate action

One business event produces two purchase actions after a webhook retry. The system must remain retry-safe without deleting audit history.

0 attempts · 0 clean pass
Read scenario
INCIDENT #OPERATIONS-05 · WEEK 5 BOSS FIGHT
READ ONLY

System is running but dashboard data is wrong

A transaction succeeds and services remain healthy, but the dashboard total is wrong. Diagnose data correctness without giving Metabase write access.

0 attempts · 0 clean pass
Read scenario
INCIDENT #RAG-06 · WEEK 6 BOSS FIGHT
READ ONLY

RAG returns 500; infrastructure root cause unknown

The RAG endpoint returns 500. Qdrant, collection configuration, Ollama, model availability, service URLs, and resources remain possible until evidence narrows the chain.

0 attempts · 0 clean pass
Read scenario
INCIDENT #AGENT-07 · WEEK 7 BOSS FIGHT
READ ONLY

Agent attempts an unauthorized sensitive action

A Sales user asks the Agent to approve its own purchase request. The Agent proposes a write tool call. Preserve audit evidence and prevent privilege escalation.

0 attempts · 0 clean pass
Read scenario
INCIDENT #RELEASE-08 · WEEK 8 BOSS FIGHT
READ ONLY

Unknown incident during release rehearsal

During a timed fresh-machine rehearsal, the main flow fails after configuration and startup. The failing layer is intentionally undisclosed. Use the frozen inventory and evidence protocol; do not edit source or delete volumes.

0 attempts · 0 clean pass
Read scenario