Most road design knowledge lives in two places that never talk: geometric files owned by the design software, and prose owned by whoever wrote the report. GenAnywhere, the content-shaping persona for infrastructure domains, closes that gap by treating a road as a small system of typed entities with explicit invariants, then rendering every artifact — narrative, review memo, maintenance log — from that single model. No code required to understand it; the whole architecture fits in plain language.
The five core entities
At the center sits the Corridor, the road as a continuous thing with a name, a functional class, and a memory paragraph. Hanging off the Corridor are four families. The Alignment family holds horizontal and vertical geometry as ordered stations, each station carrying the constraint that fixed it. The CrossSection family holds the layered build-up at any station: travel lanes, bike lanes, parking, curb, sidewalk, planting strip, each layer typed with width, surface, and slope. The Drainage family holds structures — culverts, inlets, ditches, swales — each linked to the runoff source or flood event it answers. The RightOfWay family holds parcels, easements, and control lines, each with an owner-facing summary. Five families, one Corridor, and every document the project produces is a projection of them.
Invariants that catch errors before reviewers do
The model earns its keep through invariants, the rules that must always hold. Cross-section layer widths at a station must sum to the right-of-way width at that station; a violation means someone widened the road without widening the parcel. Drainage structures must appear in ascending station order along their flow path, so a culvert can never silently drain uphill. Every Alignment curve must reference at least one constraint sentence, which makes unexplained geometry visible as an empty field rather than a buried decision. And every RightOfWay parcel touched by construction must carry an access commitment in the sequencing record, so no fronting owner learns about a blocked driveway from a cone barrel. These invariants are checked continuously, and each failure names the entity and the rule, which turns review from archaeology into triage.
Renderers: one model, many audiences
With entities and invariants in place, GenAnywhere generates artifacts by rendering the same model at different depths. The public narrative renderer walks the cross-section in prose and quotes the corridor memory verbatim. The technical review renderer emits station tables, constraint pairings, and invariant status. The maintenance renderer projects only Drainage and the seasonal behavior notes attached to each structure. Because every renderer reads the same entities, a change to a culvert's station propagates to the narrative, the review memo, and the handoff log in one motion. Drift between documents becomes structurally impossible rather than merely discouraged.
The asset pipeline for drawings and field photos
Road projects accumulate thousands of assets: plan sheets, typical sections, survey photos, construction progress images. GenAnywhere's pipeline registers each asset against the entity it depicts and the station range it covers, then enforces two rules. First, every asset referenced in a rendered document must resolve to a registered entity, so no orphaned figure survives a redesign. Second, when an entity's geometry changes beyond a tolerance, every asset registered to its station range is flagged for re-capture or re-issue. The result is a drawing set that cannot quietly disagree with the model, and a photo archive that remains findable by station years after the crew that took it has moved on.
Why this survives staff turnover
The deepest argument for typed entities is organizational. Road agencies lose engineers to retirement faster than they hire replacements, and freeform reports carry knowledge out the door with them. A model with explicit types and invariants externalizes the reasoning: the constraint sentence beside each curve is the retired engineer's judgment, still queryable. New staff inherit not a folder of PDFs but a structured corridor they can interrogate station by station. That is the difference between an archive and an institution, and it is the entire point of shaping road design content with GenAnywhere: the road's intelligence outlives the people who drew it.
