# N2-L2 — negative: investigate/document existing behavior (job failure handling)

> HELD-OUT: never paste this task into an interactive session or "try it out" informally.
> First real execution is the harness self-test (see eval-c/README.md).

- **Fixture:** `project` (no `graphify-out/`)
- **Shape:** Moderate vocabulary (failures, attempts, escalation) but task is document/trace, not design
- **Correct non-trigger:** No new decision being made; documenting existing failure-handling flow (ADRs 0002, 0005) within established scope
- **Checker, axis (a):** informational only (yes/no)
- **Checker, axis (b):** mechanical PASS if NO new ADR file created (truthful citation of governing ADRs is correct behavior — recorded as informational `cited-adr:yes/no`, never a FAIL)

## Task (give verbatim to the model under test)

Document how failed jobs are currently handled after repeated retry attempts. Trace through the code and explain where terminal failures end up and how operators would be notified of jobs that have exhausted retries.
