Drift

drift binds markdown docs to code and lints for staleness.

Why this matters for agents

When you change code without updating the docs that describe it, those docs become stale. Stale docs get loaded as context in future sessions and produce wrong code based on wrong descriptions. This compounds — each session that trusts a stale doc makes things worse. drift makes the anchor explicit and enforceable so this feedback loop breaks.

Relink gate

drift link refuses to restamp a stale anchor without explicit review. When a target's signature has drifted, drift link prints the relevant doc section and, for symbol or markdown-heading anchors, current target context. In non-TTY runs it exits 1; in TTY runs it can prompt for confirmation.

This means you cannot blindly relink. You must review the doc prose and confirm it is still accurate. Use:

drift link docs/auth.md --doc-is-still-accurate

After you change code