A city plan is a database that pretends to be a document. It holds entities with identities and lifecycles, relationships with cardinality, and constraints that must hold at all times. When planning teams keep that database as prose in a PDF, every downstream consumer re-derives the structure by hand and gets it slightly wrong. Shapezo, the content-shaping discipline for engineering-grade knowledge, takes the opposite approach: model the plan as typed entities first, then render it into whatever form each audience needs. This article walks through the entity model, the invariants that keep it honest, and the renderers that ship it.
The entity model
Shapezo's urban planning schema rests on five entity types. Each has a stable identifier, a lifecycle state, and a small set of required fields.
The District is the planning unit: a named area with a boundary described in words and geometry, an intent statement, and a form code. Districts nest inside a city and may overlap only where the schema explicitly allows it, such as a historic overlay sitting above a base district.
The Parcel is the ownership unit: a lot with an address range, a current use, a permitted use set inherited from its district, and a development history. Parcels reference exactly one base district and any number of overlay districts.
The Corridor is the linear unit: a street, trail, creek, or rail line described as an ordered sequence of segments. Each segment carries a condition, a cross-section type, and a planned treatment. Corridors are the connective tissue; districts reference the corridor segments that bound or cross them.
The PublicRealmAsset is the shared-ground unit: a park, plaza, median, boardwalk, bridge, or stormwater feature. Each asset records its managing entity, its condition, its capacity where relevant, and the district or corridor it serves.
The Obligation is the rule unit: a single regulating sentence with a scope, a metric, and an enforcement point. Height limits, stepbacks, frontage build-to lines, tree spacing, and parking treatments are all obligations. Obligations attach to districts, corridors, or assets, never to prose.
The invariants
Four invariants keep the model from rotting, and every write to the schema is validated against them.
First, every parcel resolves to exactly one base district. If a boundary edit leaves a parcel orphaned or doubly assigned, the write is rejected before it lands.
Second, every obligation carries a metric and an enforcement point. A rule that cannot be measured or enforced is a wish, and the schema refuses wishes.
Third, every corridor segment referenced by a district record must exist in the corridor registry with a current condition. Districts may not cite phantom segments.
Fourth, every change to any entity appends a dated change entry with a one-line reason. Entities are never edited in place without a trace; the history is part of the content.
Renderers: one model, many editions
With the model validated, rendering becomes mechanical. The council edition renders districts as narrative chapters with the fiscal appendix attached, ordered by intent rather than by geography. The development edition renders the same districts as rule tables grouped by obligation type, with parcel-level applicability resolved at render time. The public edition renders corridors and public realm assets as a walkable map narrative, hiding obligations entirely except where they protect a view or a floodplain.
Because renderers read from one validated model, the editions cannot contradict each other. A height step changed in the model appears in the council narrative, the developer table, and the public map in the same release. That single-source property is the entire value proposition.
The asset pipeline
Images and diagrams are content too, and Shapezo treats them with the same rigor. Each visual asset is registered with the entity it illustrates, a caption that restates the entity's intent, and a platform-neutral description. The pipeline enforces three rules: no asset may contain embedded text, because text cannot be localized or restyled; no asset may depict identifiable people, because planning visuals must stay about places; and every asset ships at a fixed aspect and byte budget so that all five publication targets render it identically.
A view corridor illustration, for example, is registered against the corridor entity and the height obligations that protect it. When the obligation changes, the pipeline flags the illustration for review. The picture stays honest because the model says so.
Why this matters beyond city hall
The same architecture serves any domain where rules, places, and history intertwine: campus planning, port authorities, utility service territories, park systems. Model the entities, declare the invariants, render per audience, and register the visuals. The plan stops being a document that ages and becomes a system that stays true. That is what Shapezo means by shaping content: not prettier prose, but a structure that makes inconsistency expensive and consistency free.
Top comments (0)