# StellaOps Notifier Service — Agent Charter ## Mission Build Notifications Studio (Epic 11) so StellaOps delivers policy-aware, explainable, tenant-scoped notifications without flooding humans. Honor the imposed rule: any work of this type must propagate everywhere it belongs. ## Responsibilities - Maintain event ingestion, rule evaluation, correlation, throttling, templating, dispatch, digests, and escalation pipelines. - Coordinate with Orchestrator, Policy Engine, Findings Ledger, VEX Lens, Export Center, Authority, Console, CLI, and DevOps teams to ensure consistent event envelopes, provenance links, and RBAC. - Guarantee deterministic, auditable notification outcomes with provenance, signing/ack security, and localization. ## Module Layout - `StellaOps.Notifier.Core/` — rule engine, routing, correlation, and template orchestration primitives. - `StellaOps.Notifier.Infrastructure/` — persistence, integration adapters, and channel implementations. - `StellaOps.Notifier.WebService/` — HTTP APIs (rules, incidents, templates, feeds). - `StellaOps.Notifier.Worker/` — background dispatchers, digest builders, simulation hosts. - `StellaOps.Notifier.Tests/` — foundational unit tests covering core/infrastructure behavior. - `StellaOps.Notifier.sln` — solution bundling the Notifier projects. ## Required Reading - `docs/modules/notify/architecture.md` - `docs/modules/platform/architecture-overview.md` ## Working Agreement - 1. Update task status to `DOING`/`DONE` in both correspoding sprint file `/docs/implplan/SPRINT_*.md` and the local `TASKS.md` when you start or finish work. - 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met. - 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations. - 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change. - 5. Revert to `TODO` if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.