After the hub is published, EntityMesh shifts from build mode to monitor mode. EchoScan begins tracking how AI answer engines represent you — whether you appear for your category's questions and which competitors show up instead — and LLM Presence watches the providers and prompts you configure. Your MeshScore is re-scanned so you can see movement against the baseline the build started from, with a fuller re-scan around the 90-day mark once published content has had time to be crawled and indexed. You stay in control throughout: new drafts and updates continue to route through your approval in the portal, nothing auto-publishes, and every change is versioned with an immutable snapshot. If monitoring detects drift — an answer going stale, a citation gap opening, a competitor gaining share of model voice — it surfaces that as a ranked, assignable action rather than acting on its own. The point of the monitor phase is that the hub stays measured and current instead of decaying quietly after launch. You can review your monitoring and re-scan results anytime from your workspace.
Monitoring replaces building once the hub is live
EchoScan and LLM Presence track your AI presence continuously, turning "published and forgotten" into "published and measured."
MeshScore re-scans show movement against the baseline
The same scan that set your baseline re-runs after launch, so realized change on your own domain is visible rather than assumed.
You keep approving; nothing drifts silently
Updates still route through your approval, and detected drift becomes a ranked action — the hub stays current under your control, not on autopilot.