The organization context
Student makers, a hackathon setting, working software, learning across experience levels, and feedback grounded in what was built.
OFFLINE FIELD CONSOLE / 01
Build less.
Build less.
Prove more.
Runway Twelve gives a wide project idea four useful edges: a pressure, a person, an observable proof, and one deliberate cut.
- 01
- Notice
- 02
- Cut
- 03
- Connect
- 04
- Relay
- 05
- Show
01THE PUBLIC SPARK
FRONTIER CASCADIA / PUBLIC CONTEXT
A room where student software has to become real.
Frontier Cascadia publicly describes a student-built Washington charitable organization centered on a high-school hackathon experience in the Pacific Northwest. Its public language emphasizes working software, honest feedback, beginner access, and taking student makers seriously.
A short build window exposes the difference between an idea that sounds complete and a path that actually runs. That tension is the creative starting point for Runway Twelve.
Visit Frontier Cascadia's current public site ↗
The private rehearsal
Scope Prism, the Build Packet, eighty Atlas modules, local favorites, rehearsal marks, and every prompt or reflection inside the app.
Official participation
No registration, schedule, eligibility, team formation, submissions, judging, prizes, waivers, mentoring, messages, or event decisions.
02SCOPE PRISM
FOUR RAILS / NO SCORE
Give an idea edges before it grows branches.
This page demo keeps selections only in the open page memory. It uses no cookies or browser storage. The Android app can save the same four predefined indexes locally when you lock a Build Packet.
01SIGNALWhat pressure repeats?
02PERSONWhose next move matters?
03PROOFWhat could someone observe?
04CUTWhat limit sharpens the test?
03BUILD ATLAS
80 IMAGE-LED MODULES
Five constellations. One project changing state.
The modules are compact decision chambers, not a course or official rubric. Enter where the build is currently stuck; leave with one move small enough to try.
Queues, duplicate work, silent failure, missing status, access edges, trust gaps, and recoverable routes.
One person, path, session, device, input, output, reversible choice, clear stop rule, and a finishable slice.
A walking skeleton, visible state, useful empty screens, boundary tests, safer defaults, credit, risk, and checkpoints.
Roles that rotate, context capsules, consent before edits, review lenses, conflict forks, merges, credit, and the last hand-off.
A real path, proof beacon, honest failure, human pace, safe sample data, accessibility, feedback, and evidence that survives the room.
04CONTEXT TRAVELS
TEAM RELAY
Speed is only useful when the next person can see the work.
Runway Twelve treats hand-off quality as part of the product. The Team Relay constellation separates correctness, clarity, and taste; makes contribution visible; and leaves room to pause when pace starts eroding respect or consent.
- Drive visibly. Say who has the next ten minutes.
- Pass a capsule. Carry goal, state, blocker, and next move.
- Review with a lens. Name whether the question is correctness, clarity, or craft.
- Leave a trail. Make the project understandable after sprint energy disappears.
05DEMO RUNWAY
OBSERVABLE STATE
The product should carry the story.
A demo begins with the pressure, walks the actual path, pauses on the proof, names a boundary, and ends on the state worth remembering. It does not need to pretend every edge is finished.
BEFOREPATHPROOFBOUNDARYNEXT CUT
06THE FLIGHTCASE
PRIVATE BY SMALL DESIGN
Keep the route, not the identity.
The Android app stores only four selected indexes, whether a packet is locked, and the numeric IDs of favorited or rehearsed Atlas modules. It provides no free-text field for an idea, name, school, repository, team, or event information.
NO ACCOUNTNO ADSNO ANALYTICSNO NETWORK PERMISSIONNO BILLINGNO PERSONAL-CONTENT INPUT
Read all 18 policy sections
RUNWAY TWELVE / OFFLINE
What can your next build prove?
Start with one pressure. Give one person a finishable route. Let one product state answer back.
Refract a packet