SUMMARY: A drift map records where a system has moved away from its original purpose, label, or trust condition.
Drift rarely arrives as a single event. A chat room gains a second use. A forum rule stretches to cover a new pattern. A source list keeps working after its purpose has changed. A page title remains accurate in grammar but inaccurate in context.
The map matters because drift hides inside continuity. The surface looks stable while the operating reality underneath has moved.
Map Points
Surface: the page, room, feed, account group, setting, source list, or archive route being reviewed.
Original purpose: what the surface was meant to do when it was created or last reviewed.
Current use: how people, bots, search engines, or operators are actually using it now.
Correction path: relabel, retire, split, document, restrict, or promote into a durable rule.
Operating Use
Use drift maps during morning administration, source rotation, registration review, and interface repair. They connect permission drift with the audit trail.
Operator Rule
If a surface still looks the same but behaves differently, map the drift before fixing the surface.
Field assessment: drift becomes manageable once it has coordinates.