Initial public ModelForge release
This commit is contained in:
@@ -0,0 +1,17 @@
|
||||
# ADR-0039: Deduplicated alert lifecycle
|
||||
|
||||
## Status
|
||||
|
||||
Accepted in M14 on 2026-08-27.
|
||||
|
||||
## Decision
|
||||
|
||||
Use immutable versioned rules and deterministic logical fingerprints with pending, firing,
|
||||
acknowledged, resolved and maintenance-suppressed states. Every transition is durable; M14 performs
|
||||
no automatic destructive remediation.
|
||||
|
||||
## Consequences
|
||||
|
||||
Polling does not produce alert spam, acknowledgement cannot erase evidence, recovery stays visible
|
||||
and maintenance cannot silently disable monitoring. Lightweight incidents claim causality only for
|
||||
evidenced node/downstream relationships.
|
||||
Reference in New Issue
Block a user