Drift detection
How Modus flags docs that a project change made stale.
When your project changes, whether through new code, a deploy, or a contract, docs can fall out of date. Drift detection flags which ones a given change likely made stale, so outdated docs surface instead of quietly misleading.
What triggers a check
A lightweight, fire-and-forget check runs after meaningful changes:
- Code: file changes after a chat turn
- Deploy: after a deploy completes
- Token Launcher: when a contract artifact changes
- PRD: after post-approval changes
How it decides
Modus pulls the headings from your existing docs and asks a fast model which ones a given change made wrong or incomplete. Affected docs get a drift reason and a timestamp. It's deliberately cheap and advisory: a hint, not a hard gate.
What you see
A drifting doc shows a warning banner with the reason and an Ask the agent to refresh action. On the hub, the Docs card shows a drift count when any docs are stale.
Clearing drift
Saving a doc, whether you edit it yourself or the agent refreshes it, clears its drift flags and marks it current again.