Notifier — Architecture (retired; superseded by the Notify dossier)
FROZEN 2026-09-08. This dossier described a host family that no longer exists.
SPRINT_20260722_015NTF-10 retired the Notifier predecessor after a constructed forcing function proved the successor delivering. The sources are frozen atsrc/__Obsoleted/Notifier/under CODE_OF_CONDUCT §15.4; the freeze record there names the ruling, the salvage list and every reference severed on the way out.The current architecture dossier is
../notify/architecture.md. Nothing in this file should be read as a description of running software.
Where each part of the old dossier went
| The old dossier covered | Now described in |
|---|---|
The two src/Notifier/ projects and how they composed the Notify libraries | ../notify/architecture.md— one WebService plus the notify-worker role over StellaOps.Notify.Delivery |
| Event ingest, rules, channels, templates, escalation, digest, storm-breaker, quiet hours | ../notify/architecture.mdand the topic pages beside it |
| Persistence and queue boundaries | ../notify/architecture.md, plus ../../architecture/database-ownership-matrix.mdfor stellaops_notify |
| Dev SMTP loop (Mailpit fall-back) | ../notify/operations/dev-smtp.md |
| Operator procedures | ../../runbooks/notify/notifier-runbook.md |
Why this file is a pointer rather than a preserved design record
The Notifier capability was consolidated, not withdrawn: every behaviour this dossier described is still shipped, by notify-web and notify-worker. Keeping a second architecture document for the same behaviour is the ambiguous-dual-home defect AGENTS.md §2.9 forbids, and a reader landing here from an old link needs the current dossier, not a snapshot. The design history that is genuinely gone with the predecessor — its composition roots and the divergent rollback copy of the API — is in the frozen tree and in git log --follow over it.