Doc & decision drift

Drift detection warns you when your docs or recorded decisions no longer match the code they describe.

Documentation rots the moment code moves on. Because Altretta holds your code and your notes in one signed graph, it can compare them — and tell you when they've fallen out of sync instead of letting you trust a stale doc.

Why Altretta can catch this

A wiki has no idea what your code looks like, so it can never know its own pages went stale. Altretta does: the symbol graph and the notes that reference it are connected in the same signed graph. When the code behind a decision changes, Altretta can see that the note and the source no longer agree — and flag it.

What it warns you about

• Docs that describe code that changed — a how-it-works note pointing at a function whose behavior or shape has moved on.
• Decisions overtaken by the code — a recorded decision the current implementation no longer honors.
• References that no longer resolve — a note pointing at a symbol that's been renamed or superseded.

Drift you can prove

Because every ingest records its git provenance in the signed DAG, drift is anchored to real history: Altretta isn't guessing that things changed, it can point to the code state that a doc was written against versus the code state now. See Signed history.

Related