For most of the twentieth century, a zoning ordinance was a PDF and a fight. Setbacks, floor-area ratios, daylight angles and use mixes lived as prose in a binder, and every test of “what if we moved the tower five metres east” meant a planner, a draughtsman and three weeks. The quiet shift now underway is this: those rules are becoming executable. Write the envelope, the sunlight target and the street-frontage rule as a handful of parameters, and the masterplan recomputes itself.

This is not speculative. It is the same move PAZ has documented at building scale and is now scaling up to the block. In our coverage of See Architects’ Nonhyun 169 in Seoul, Kee Lew’s team treated the four-storey cap and below-average FAR not as a constraint to dodge but as Layer Zero — a locked red Rhino solid from which every later decision is a subtraction. Parametric urbanism simply promotes that solid from one parcel to a thousand. Feed in the cadastre, the regulatory geometry and a few performance targets, and the model returns massing, shadow maps and ground-floor activation as live functions you can re-run, not drawings you redraw.

←TODAY: In 2026, Grasshopper + Ladybug already turn FAR, setbacks and solar access into a recomputable 3D solid before schematic design. →3012: The Zurich-3012 masterplan rezones nightly, its arcology envelopes re-solved against shadow, mesh-traffic and street-life telemetry while the city sleeps. Fulcrum: A rule you can run is a rule you can audit — the same script that generates the envelope proves it was legal.

The deeper lesson comes from what happens when rules are not code. Our piece on San Francisco’s Embarcadero Freeway traced how a plan optimised for a single variable — traffic throughput in the 1948 Trafficways Plan — treated waterfront economy and pedestrian severance as externalities with no feedback loop. It took an earthquake to force the recompute. Zoning-as-code makes the externality visible at the decision stage: pedestrian comfort, solar access and frontage become parameters in the same model, not afterthoughts in a different department.

The danger is the obvious one. A masterplan that recomputes from “a handful of rules” is only as humane as the rules you chose. Optimise for FAR alone and you rebuild the Embarcadero in code, faster. The discipline is in what you make a parameter — and in refusing to let the elegance of the script smuggle in a thin model of the street.

Atelier: Build your zoning envelope as Layer Zero before anyone draws a plan — a single Grasshopper solid carrying setback, height cap, FAR and a Ladybug solar-access target, locked and named. Every subsequent move is then a legible subtraction from a volume the regulator could verify, which is exactly the workflow Alina McConnochie’s parametric HYPERMIX housing study uses to keep balcony depth, window ratio and contour all live at once.

Hack: This Hack teaches you to compute a buildable envelope volume from zoning rules in three lines — the smallest possible “zoning as code.” The domain is geometry: a setback shrinks the footprint, the height cap and FAR fight over how tall you may go. Drop this into a Grasshopper Python component or a plain console; swap in your parcel’s numbers.

site_area, setback, frontage, depth = 1200, 4, 40, 30   # m², m
footprint = (frontage - 2*setback) * (depth - 2*setback)
max_far_floors = (site_area * 2.5) / footprint           # FAR 2.5
print(round(footprint), "m² plate,", round(min(max_far_floors, 6)), "floors")  # cap 6

Change the FAR from 2.5 to 3.0 and watch the floor count jump without touching a single line of geometry — that is the whole promise. The rule is now a function, the function is now testable, and the masterplan is now an argument you can lose on the merits rather than in the binder. Open Rhino tonight, model your worst regulatory parcel as a locked solid, and make the ordinance run.