Before it was a city, Chandigarh was a diagram. Punjab lost its historic capital, Lahore, to Pakistan in the 1947 Partition, and in 1951 the Indian government handed Le Corbusier — working with Pierre Jeanneret, Jane Drew, and Maxwell Fry — a half-drawn scheme: Albert Mayer and Matthew Nowicki’s fan-shaped, Garden-City layout, abandoned after Nowicki died in a 1950 air crash. He redrew it as a rectilinear grid. As architecturelab.net documents, he described the result as a human body: the Capitol Complex the “head,” Sector 17 the commercial “heart,” the parks its “lungs,” the road network its circulatory system. Read that metaphor the way a systems engineer reads it and you get something sharper than poetry: a dependency graph, with every organ hanging off one hierarchical spine.

That spine is the 7V system — a strict hierarchy from V1 regional highways down through V3 sector-boundary roads to V7 pedestrian paths, each level feeding the next. It is elegant, legible, and — in graph terms — a tree. Trees have a property Le Corbusier’s body metaphor accidentally makes literal: cut one artery and everything downstream loses supply. The sector, his fundamental unit at roughly 800 by 1200 metres, is a self-contained cell — a hand-drawn Voronoi tessellation before the math had a name — but it reaches the whole through a small number of V3 gates. Fewer connections mean cleaner traffic. They also mean more single points of failure.

←TODAY: Chandigarh’s plan sized the city for 500,000; the metropolitan area now runs far past that, straining a grid whose monumental concrete is aging — The Tribune reported roof leaks in a Capitol-adjacent museum flagged in the Lok Sabha. →3012: the cities that survive are the ones whose dependency graphs were drawn honestly, not the ones whose diagrams looked cleanest. Fulcrum: a hierarchy is only as resilient as its least-redundant node, and you cannot see that node on the architecture drawing — only on the graph.

This is why the body metaphor is worth more than nostalgia. One generation read Chandigarh as sculpture; Koolhaas, in Delirious New York, taught the opposite habit — read the city as a found system to be theorised, not a composition to be admired. The 7V hierarchy is a found system, and its failure modes are knowable. The V3 that rings each sector is the choke point; the Capitol Complex, as head, is the textbook single point of failure — concentrate the Secretariat, High Court, and Legislative Assembly on one monumental plateau and you concentrate the risk with them. When local authorities rejected Le Corbusier’s high-rise Unité d’Habitation blocks and had Jeanneret, Drew, and Fry design lower-density housing instead, they were, unknowingly, decentralising one layer of the graph.

Atelier: Your Büro runs on the same topology, and you have almost certainly never drawn it. The render node, the licence server, the one senior who holds the Grasshopper definition, the single Speckle stream every model syncs through — that is your private 7V system, and its choke points are invisible on any org chart. Monday move: spend twenty minutes drawing your office’s real dependency graph — not the architecture diagram, the graph of what-breaks-what — and mark every node whose loss stops production. The third one you find is the point of the exercise.

Hack: List every road whose loss severs a Chandigarh sector from the grid — the articulation points — in three lines of Python. Model the 7V hierarchy as edges, then ask networkx which nodes are cut vertices: remove any one and the graph splits into disconnected pieces. Swap in your own studio’s dependencies and read the list as a risk register.

import networkx as nx
g = nx.Graph([("V1","V2"),("V2","V3"),("V3","V4"),("V4","V6"),("V6","house")])
print(sorted(nx.articulation_points(g)))

Every node prints — a pure tree has zero redundancy, which is exactly the warning. Add one cross-link (a second route into the sector) and watch the list shrink.

Le Corbusier’s grid still shapes the Shivalik-foothills capital seventy years on, which is the measure of a strong diagram. But strong is not the same as resilient. The lesson this master plan leaves on your desk is not aesthetic; it is topological. Draw the graph, find the cut vertex, add the redundant edge before the day you need it — do it for one system in your office before you leave the desk today.

Source: architecturelab.net