AMAROK is the remediation tracker — watching every proposed fix from the moment it's approved through to verified closure. It reads navi.db to confirm that patches landed, tags were written, and findings actually closed — not just marked done.
Capabilities
- Tracks open remediations from approval to verified close against navi.db
- Confirms tag and patch application by re-querying findings post-remediation
- Surfaces stalled and overdue items with owner context
- Gated remediation report — proposed, previewed, sent only on confirm
What AMAROK Tracks
AMAROK watches the gap between "approved" and "done" — the stalled ticket, the patch applied to the wrong host, the tag written but never verified. It closes the loop the rest of the pack opens, using navi.db as the ground truth.
Why It Matters
Approving a fix is not the same as verifying it. AMAROK re-queries the estate after every remediation window to confirm closure — with a paper trail and a human gate before anything is reported as done.
Gate Model
Every remediation report is proposed and previewed before delivery. AMAROK requires explicit per-call confirmation. Works entirely from navi.db — no external feeds, no guesswork.