The Map Was Right, Once
When the Queen ascended, Naksha the cartographer made a perfect map of every road, well, and garrison in the kingdom. The map was the source of truth. Armies marched to positions the map described. Supply routes followed the map's roads. The map was correct on the day it was drawn, and for a month after that. Then Grameen the village headman built a new bridge — it was faster than asking the capital. He did not tell Naksha. A road washed out; no one updated the map. A garrison was moved; Naksha was not informed.
“A map unmaintained is a lie with authority.”
The Drift
By the third year, the Queen's army marched to a garrison that had moved. A supply cart followed a road that ended in a marsh. A well on the map had been filled in by a farmer who needed the land. None of the discrepancies were large. Each one was someone's reasonable local decision. But the drift had accumulated silently. The map said one thing. The kingdom was another. The Queen sent for Pariksha the inspector and said: "Walk the entire kingdom. Tell me every place the map is wrong."
“Drift does not announce itself. It accumulates silently until someone looks.”
The Inspection Plan
Pariksha walked for thirty days and returned with a list of discrepancies. She did not fix them — her role was to report. She gave the Queen two columns: "What the map says" and "What I found." The Queen could now decide: update the map to match reality (accept the drift), or change reality to match the map (remediate). Some drifts were harmless — a well moved fifty paces. Some were dangerous — a garrison reduced by half in a border region. The plan alone, without any action, was valuable. You cannot fix what you cannot see.
“Detecting drift and remediating drift are two separate skills. Earn the first before attempting the second.”
The Scheduled Walk
After the first inspection, the Queen did not wait for a crisis. She scheduled Pariksha to walk every road every fortnight, carrying the current map. Pariksha compared what she saw to what the map said and reported differences every fourteen days. Most reports said: "All matches." Occasionally: "Grameen has built a new well — the map does not show it." The discrepancy was small and fresh, not thirty accumulated changes compounded over years. The Queen updated the map promptly. The gap between map and kingdom never grew large again.
“Scheduled inspection contains drift; crisis inspection merely reveals it.”
The Law That Prevented Drift
Pariksha suggested a new law: any headman who changed a road, well, or garrison must file notice with Naksha within three days or face a fine. Most headmen complied. Drift fell further. But some changes were still made in haste during floods and emergencies and never reported. So Pariksha proposed a second measure: a standing patrol that checked the five most critical roads every week. These were the ones an army depended on. Critical infrastructure was checked constantly. The rest was checked periodically. The law prevented drift at the source. The patrol caught what the law missed.
“Detect what you cannot prevent. Prevent what you can detect early.”
The Map That Trusted Itself Again
The Queen lived to old age and passed the map to her daughter. The new queen opened Naksha's chest and found a map she could trust — not because nothing had ever drifted, but because the drift was found quickly and the map was updated promptly. The new queen's first campaign was her fastest. She never marched to a garrison that had moved. The bridge Grameen built was on the map, because Grameen had reported it. The map was not perfect. But it was close enough to trust. And trust, in a kingdom that moved armies, was worth more than perfection.
“A map continuously reconciled is more valuable than a perfect map drawn once.”
🪔 Deepak — the lamp of meaning · what this fable means in code
Infrastructure drift is the gap between what your IaC describes and what is actually deployed. It happens through manual portal changes, hotfixes applied directly to resources, and incomplete rollbacks. Terraform's drift detection is terraform plan — it compares state to reality and shows differences without applying changes. Scheduled plan-only runs in CI catch drift continuously. Azure Policy provides enforcement — it can prevent resources from leaving a compliant state, not just detect when they do. The insight: detection and enforcement are complementary tools. Run detection on a schedule; use enforcement for your most critical configurations.