Programs
NEST does not operate as a stack of disconnected activities. It runs a small number of serious programs with distinct structures, timelines, and outputs. Each one is designed to create visible work that can be built, tested, published, reviewed, or continued.
Program Index
NEST runs fewer programs on purpose. Each one is meant to hold more structure, sharper standards, and more visible output than a generic activity list.
Hackathon
The hackathon is structured as a temporary studio rather than an open-ended event. Teams apply with a direction, build under time pressure, and present work against a standard of clarity, rigor, and execution.
Baekho Racing
Baekho Racing is organized around machine performance, subsystem logic, documentation, and iteration. It is treated as a serious engineering program rather than a display object.
District Zero
District Zero places student teams in contact with spaces, stakeholders, and implementation realities so the work has to survive beyond concept-level design.
Live Status
These are the current operating states across the NEST program stack.
Hackathon
Tracks, rules, and review criteria are published. Teams can now apply through the formal intake route.
Baekho Racing
Powertrain, controls, sourcing, and documentation are moving through current-cycle build logic.
District Zero
The civic build program is forming around real sites, outside constraints, and implementation partners.
Publications
The research journal is assembling founding pieces, editorial criteria, and contributor pathways.
Operating Notes
The institution should be legible through current states, not only by description.
Hackathon applications are the primary live intake route.
Baekho is in subsystem planning, sourcing, and test logic definition.
District Zero is moving through partner outreach and program framing.
Publication standards are being set before broader contributor intake.