Self-healing documentation
Self-healing documentation is product knowledge that repairs itself as the interface changes, instead of decaying between manual edits. It is the outcome of drift detection: when a route's confidence falls, the system re-reads the live product, merges a rename automatically, and flags a restructure for review, so the answers stay true without a doc-writing cycle.
How can documentation heal itself?
By being grounded in observation rather than prose. When knowledge is a live map of the interface scored on every session, a change in the product is a change in the map. A renamed button updates the moment it's re-read; there is no separate document to remember to edit, so the gap between product and docs never opens.
What still needs a human?
Structural change. A rename merges automatically because the intent is unambiguous, but a page that was split into three, or a flow that gained a step, waits for a short confirmation so a person can approve the new shape. The system heals the routine drift and escalates the genuine redesign.