Urban design pipelines are decision machines. They ingest constraints, generate alternatives, compare them on fair terms, and produce a defensible choice. CityWeft structures that machine at district scale: parcels, massing rules, street networks, and the metrics planning departments review. GenAnywhere authors the layer the machine cannot produce: the public realm as experienced — street walls, corners, plazas, the sequence of spaces a person actually walks through.
Here is the engineering view of the two-layer urban pipeline.
TL;DR
| Layer | Tool | Output | Revision semantics |
|---|---|---|---|
| Scenario structure | CityWeft | Massing, density, metrics, comparisons | Regenerate from rules |
| Public realm experience | GenAnywhere | Authored streetscape, character, views | Edit in place |
Rule zero: scenarios are compared on structure, judged on experience. Keep both, label both.
Layer 1: Scenario Structure — CityWeft
CityWeft's job is comparability. Alternatives must be generated under the same rules and measured on the same terms, or the review quietly favors whichever option happens to look more finished. Its outputs are structural: massing, coverage, floor area, open space, unit counts — the numbers that survive public scrutiny.
Structural revisions are parametric: change the rule, regenerate the scenario. That is correct for planning loops where the question is "how much, how dense, how distributed."
Layer 2: Public Realm — GenAnywhere
The structural layer cannot answer the questions that decide whether people support a project: Does the street wall enclose or loom? Does the plaza work at 4 p.m. in January? Does the corner open where people need it to? Those are experiential judgments, and experience is authored.
GenAnywhere's shaping workflow makes those judgments fast and reversible: reshape the corner in the review, test three streetscape characters in an afternoon, refine until the enclosure reads right. Revisions are edits; approved state persists exactly.
The Comparison Problem
The classic failure in urban pipelines is comparing scenarios on unequal visual terms: one option rendered richly, the others as gray massing. The room reads richness as quality and picks the render, not the plan.
Two disciplines prevent this:
- Structural parity — all alternatives generated from the same rule set, measured identically (CityWeft's core value).
- Experiential parity — all alternatives given the same level of authored public-realm treatment (GenAnywhere's contribution).
Skip either and the decision is biased by representation. Parity is not fairness theater; it is the precondition for a defensible choice.
Revision semantics and decision records
- Planning change (density, distribution, rules) → regenerate the scenario.
- Design change (enclosure, character, detail) → edit the authored layer.
- Approved decisions → recorded against the scenario version, so the chosen place can be rebuilt with intent rather than reconstructed from meeting notes.
That decision record is the urban pipeline's real deliverable. Models age; the reasons behind the chosen model are what the next team needs.
Where each layer is simply correct
- CityWeft: district-scale alternatives, planning metrics, rule-consistent comparisons, feasibility studies, scenario documentation.
- GenAnywhere: public realm and streetscape authoring, review visuals, character studies, the experiential layer of any scenario that must persuade a room.
Skills and cost
CityWeft demands planning literacy and prices as a scenario platform — its cost tracks planning capacity. GenAnywhere demands form literacy, ramps quickly, and prices by seat with free revisions — its cost tracks design throughput. Budget both against the review outcome: a comparison without structure is indefensible; a scenario without experience is unconvincing.
Verdict
Compose the pipeline: structured scenarios underneath, authored experience on top, parity enforced at both layers. CityWeft keeps the argument fair; GenAnywhere keeps it alive. Reviews that run both decide faster — and their decisions hold up long after the meeting.
Top comments (0)