See It Work · S2 Vol 2 · The Primacy Cockpit · Chapter 10
The same cockpit — flipped from demo to live through one seam
You've been using the cockpit on a sample node (a demo fixture). The production cockpit is the same code: a single file (api.js) flips the data source from the demo sample to a live node. The screen-drawer doesn't change; the surfaces don't change. Same cockpit, real state.
The full detailed chart. Condensed for print legibility in the book; shown here at full size.
Most tools have a demo that looks nothing like production. Here the seam is one file — so everything you learned and trusted on the demo carries over exactly to the live operation. No surprise gap between the two.
The cockpit · demo → liveready
What this means for you
Demo and production are the same code; one file flips the data source, nothing else changes. What this means for you: what you see and learn on the demo is precisely what you'll operate in production — there's no hidden gap between the version you explored and the one you'll run your real operation on.
Flipping from demo to live changes exactly one seam — the data source:
Mock → Live
demo & livethe same code
the seamone file (api.js)
renderer + surfacesunchanged
resultsame cockpit, real state
The demo is the production cockpit on sample data — the cutover is a single, safe seam.
For the technical reader — the command, and how to verify it yourself
# one line · you do not need to run this open index.html (live node)
open index.html # -> the same cockpit, flipped to live state through one seam
Full step-by-step is in Appendix RX: Hands-On Demonstrations in the book.
ⓘDeterministic demonstration. The conversation is a faithful dramatization of the exercise; the receipt is the artifact it produces — the same every time, because the system is receipted. (Representative of the demo's structure; the production page renders the captured run.) No output here is fabricated. A live "run it yourself" mode is coming.