The Rigid Blueprint

In the old days, the Rajah's builders raised palaces by shouting commands at craftsmen. "Add a pillar here. Move that wall. No — move it back." Months passed. No two palaces were alike. The second palace differed from the first in a hundred ways no one could explain. The Rajah grew tired of paying twice for the same mistake. He summoned Lipika, the royal scribe, and said: "Write everything down before a single brick is laid."

Lipika wrote a manuscript for the next palace. Not a sketch — a manuscript. Every pillar's height. Every gate's width. The number of wells. The depth of the foundations. The order in which each part must be assembled. She used a precise language, JSON, in which every brace must be closed, every key must be quoted, and nothing could be left to imagination. The manuscript was long — two hundred pages for a modest palace. But when Rachaka the builder opened it, he knew everything. He never had to ask.

The Rajah wanted three palaces: one in the north, one in the south, one in the east. They should be identical in design but different in size and colour. Lipika wrote one manuscript with blank spaces at the top — parameters — and asked the Rajah to fill them in for each palace: "northSize: large, northColour: white." The rest of the manuscript was unchanged. Deep inside the manuscript she kept calculated values in variables, so the same number was never written twice. Change the parameter, and the variable rippled through every page.

Rachaka learned early that some things could not be built in any order. A door cannot hang before the wall is raised. A well cannot be dug inside a floor. Lipika added a special instruction to each section: dependsOn. "This gate depends on this wall. This floor depends on these foundations." The forge read dependsOn and arranged the craftsmen accordingly. Two sections with no dependency between them were built at the same time. Sections that depended on each other waited. The palace rose in the right order, always.

Years passed. The Rajah's son inherited the kingdom and wanted to rebuild one palace. The craftsmen were new. The old builders had retired. But Lipika's manuscripts were still in the vault. The son sent for Rachaka's apprentice, handed him the manuscript, and said: "Build this again." The new craftsman read the manuscript and built it exactly. No guess. No improvisation. The blueprint was the palace, described in advance. A new scribe named Bicep had started writing shorter manuscripts — she called them sugar for the same blueprint — but the old manuscripts still worked, still ran, still built the same palace, year after year.

Lipika's manuscripts were long and exacting. They did not allow partial changes — to change one room, you described the whole palace again with that room changed. The Rajah's new advisor suggested Bicep for new palaces. But Lipika reminded him: "Every Template Spec I filed here can be reused by any builder in the kingdom with a single reference. My manuscripts are the law — Bicep merely speaks in shorter sentences. The forge understands both. Choose the format that suits your scribes, but understand that they both produce the same palace."