See It Work · S2 Vol 2 · The Primacy Cockpit · Chapter 8
All your hats, side by side — never blurred
Many operators carry more than one mandate — corporate, family-office, civic. The cockpit renders each as its own strip, side by side. You move between them without one mandate's data bleeding into another, you see where your nodes collaborate, and any cross-mandate handoff leaves a receipt.
The full detailed chart. Condensed for print legibility in the book; shown here at full size.
Blur your mandates on one screen and you blur the audit — and risk one hat's data leaking into another. Keeping them as distinct strips, with receipted crossings, keeps each mandate cleanly sovereign.
The cockpit · multi-mandate stripready
What this means for you
Each mandate is its own strip; crossings are receipted; nothing bleeds. What this means for you: you can run several roles from one cockpit and keep them cleanly separate — your company and your family stay distinct worlds, and any time work crosses between them, there's a receipt to prove exactly how.
Each mandate renders as its own strip; cross-mandate work leaves a receipt:
Multi-Mandate
each mandateits own strip, side by side
switchingno data bleed
collaborationvisible per mandate
crossingsreceipted — never a quiet blur
Mandates without bleed — one operator, distinct sovereign surfaces.
For the technical reader — the command, and how to verify it yourself
# one line · you do not need to run this open atrium-standalone.html
open atrium-standalone.html # -> each mandate its own strip, crossings receipted
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.