Restructure solution layout by module
This commit is contained in:
17
src/Notifier/StellaOps.Notifier/AGENTS.md
Normal file
17
src/Notifier/StellaOps.Notifier/AGENTS.md
Normal file
@@ -0,0 +1,17 @@
|
||||
# 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.
|
||||
Reference in New Issue
Block a user