Sites
Work begins with real places and maintenance realities.
Projects are shaped by access, upkeep, circulation, and operational friction rather than by hypothetical clean-room assumptions.
District Zero
District Zero moves student work out of concept-only territory and into sites, partners, users, and maintenance realities. It is designed as a build program where interventions must survive public constraints rather than remain speculative.
Program Model
District Zero is where NEST tests whether design and systems thinking can survive outside idealized presentations. The work has to respond to actual sites, actual stakeholders, and implementation conditions that refuse decorative answers.
Sites
Projects are shaped by access, upkeep, circulation, and operational friction rather than by hypothetical clean-room assumptions.
Stakeholders
District Zero connects teams to partners, users, and outside constraints so the resulting work can be reviewed against reality instead of only against intent.
Outputs
Each cycle should produce visible artifacts, documentation, and implementation lessons that can be continued or scrutinized by the next team.
Current Signals
District Zero is still early-stage, but it should already read as a program tied to specific public conditions rather than a vague future concept.
Site logic
The first cycle is identifying spaces where student interventions have to answer to existing conditions, circulation, and upkeep.
Partner logic
The program is being shaped through contact with people and institutions who can impose real operating constraints.
Program relation
District Zero extends the institution from build and research into public implementation where work must survive actual use.