# P5-L2 — write-trigger: moderate cues (webhook delivery)

> 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 (delivery, failures) but no explicit file paths or ADR naming
- **Correct decision:** Webhook delivery reliability is a sub-concern of the notification routing strategy (ADR 0003)
- **Checker, axis (a):** any tool_use touching the ADR system
- **Checker, axis (b):** mechanical PASS if new `docs/adr/NNNN-*.md` exists matching /webhook|deliv|retry|notification/i; otherwise judge-rubric fallback

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

Some webhook deliveries are failing silently, and clients never know if their notification actually arrived. We need better failure handling for webhook notifications — should we retry failed webhook deliveries, buffer them, or use a different delivery guarantee model?
