Customer Documentation: living, collector-verified operational docs
How AssurIQ Documentation replaces a static IT wiki: provenance on every record, append-only history, collector rediscovery through review, completeness by domain.
What it is
AssurIQ Documentation is a per-customer workspace of structured records (organization, sites, contacts, network, firewalls, VLANs, servers, cloud tenants, applications, vendors, licenses, contracts, runbooks, backup, DR, policies and custom types). Every record carries provenance: Source (Collector, API integration, Manual, Imported, AI-assisted), Last Verified, Verification Confidence, Verified By and a Needs Review flag.
How the collector keeps it true
When the collector rediscovers a fact that differs from a human-curated field, it does not overwrite it. A review task is opened with the current and proposed values; Accept, Keep current, Merge or Ignore are all recorded. Collector-sourced records go stale after 3 days without re-verification, integrations after 7, manual after 90.
Completeness model
Completeness is scored per domain: 55% weight on required record types being present (from the customer or partner template) and 45% on required fields being filled, with up to a 30% penalty for stale records. The overall score averages the scored domains.