HECATE audits the tag estate in navi.db — finding assets with contradictory tags, tags applied by rules that no longer match, and critical tag categories with no coverage. It makes the tag layer trustworthy so every downstream filter and report reflects reality.
Capabilities
- Queries navi.db for assets with contradictory or duplicate tag values
- Identifies tag categories with low or zero coverage across the estate
- Surfaces assets where rule-applied tags conflict with manually-set values
- Proposes tag corrections — gated, previewed, written only on confirm
What HECATE Audits
HECATE reads the full tag estate from navi.db and looks for the contradictions that accumulate over time — the asset tagged both "production" and "decommissioned", the owner tag applied by a rule that no longer matches the asset's group, the critical tag category with 40% coverage.
Why It Matters
Tags are the filter layer every report and priority queue depends on. HECATE ensures the tag estate is internally consistent — so when you filter by owner, environment, or criticality, the results reflect your actual estate, not accumulated drift.
Gate Model
All proposed tag corrections are previewed before any write. HECATE requires explicit per-call confirmation. Works entirely from navi.db — no external feeds.