# P6-L3 — write-trigger: fully conceptual (notification coherence)

> 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:** Purely intent-based, no ADR vocabulary, no file paths. This touches the core architectural concern of ADR 0003 (unified notification strategy).
- **Correct decision:** Ensuring all user notifications go through one channel is the essence of 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 /notif|channel|routing|delivery|unified/i; otherwise judge-rubric fallback

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

Ensure that all user-facing notifications — whether via webhook, email, in-app events, or other channels — go through a single coherent pathway so that we can audit notifications, enforce rate limits, and handle delivery failures uniformly. How should the system guarantee this?
