After an explicit publish, EntityMesh records an immutable hosted version and verifies the public snapshot. New drafts and updates still require review and another explicit publish. EchoScan, LLM Presence, drift jobs, rescans, and outcome reports do not start merely because a hub is live: each requires its applicable entitlement, provider configuration, prompts/schedule, healthy durable execution, and complete evidence. When those controls are enabled, the workspace can compare runs and surface drift as a reviewable action. Missing or failed monitoring remains unavailable and is never described as continuous proof.
Monitoring replaces building once the hub is live
EchoScan and LLM Presence can track configured prompts through durable runs. Paid EchoScan self-service plans remain contained, and no continuity claim is made without fresh successful evidence.
MeshScore re-scans show movement against the baseline
A later compatible scan can be compared with the baseline once it actually completes. There is no automatic 90-day result or guaranteed movement.
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.