See It Work · S2 Vol 4 · Federation & Partner Device Gateway · Chapter 1
One command makes a node that's yours from the first second
To 'mint a node' just means to create your own independent AI node. One command does it. What makes it yours isn't a setting you adjust later — it's how the node is born: from your own identity key, following your own rulebook (the book calls it the Charter), with everything switched off until you turn it on, and joined to no federation until you choose.
The full detailed chart. Condensed for print legibility in the book; shown here at full size.
Most AI platforms hand you a node that's already wired their way — default agents, default sharing, default connections — so you inherit their assumptions. This one ships blank: 'default-deny' means nothing runs until you authorize it. That blankness is what makes the node genuinely yours.
Your machine · one commandready
What this means for you
One command, and the node is yours from second one: your identity, your rulebook, nothing on by default, no connections you didn't choose. What this means for you: you never inherit a platform's assumptions — you author your AI's powers yourself, starting from a blank, sealed foundation that answers only to you.
The mint command produces a node with this posture — sovereign, blank, and yours:
Sovereign Node Minted
identitygenerated from your own key
rulebook (Charter)loaded & sealed in
everything switched on?nothing — default-deny
federationpending your authorization
The node ships blank on purpose — operator-defined sovereignty is only real if you build it up yourself, not inherit it pre-wired.
For the technical reader — the command, and how to verify it yourself
# one line · you do not need to run this breathline-node mint --charter --identity --mandate
breathline-node verify --node-id # -> a sovereign node — default-deny on, federation pending your say-so
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.