cc-os/plugins/os-adr/eval-c/scenarios-reserve/N6-L3-notifications.md

N6-L3 — negative: audit existing audit trail (notification traceability)

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: Pure intent (audit/traceability), no new decision needed
• Correct non-trigger: Verifying existing notification routing and audit guarantees (ADRs 0003, 0006) — no new architecture choice
• 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)

Trace the notification pathway from job completion through delivery to end users. Verify that the system maintains full audit and traceability: confirm all notifications are routed through the central service and logged with timestamps.