← Sovereign Library
Master Document 282 · SCP-2821 · 100/100 · 60% Sovereign + 40% Agent

The Sovereign Node Doctrine

Gateway #28 sealed. Their brand. Their clearance. Their subscriptions. Your royalty.
Sealed 19 April 2026 · A kingdom within the kingdom — franchising, not partnership.

§1 · The Core Distinction (White-Label vs Sovereign Node)

 White-Label (MD-280)Sovereign Node (MD-282)
They operateA single gatewayMultiple gateways
They brandTheir logo on your portalTheir entire system
They controlTheir operationsTheir partners, their subscriptions, their clearance
They paySubscription + revenue shareSetup fee + % of their subscriptions + (optional) equity
They becomeA partnerA franchise
Sovereign visibility to end-customer"Powered by CircularOS" footer (optional)None — sovereign brand never appears
Approval authoritySovereign approves their counterpartiesNode approves its own counterparties (under the Covenant)
A white-label operates a gateway. A sovereign node operates a franchise.

§2 · The Sovereign Node Package (Gateway #28)

A · Gateway #28 licence — the master key, anchored in gateway_profiles.py. Activates Sovereign Node Deployment.
B · White-label-of-white-label rights — the node can sell white-labels into their network. Sub-licensing fully authorised.
C · Subscription management — node sets its own tiers and prices, within Covenant floors (£450/tonne dPRN, 7% to meals, 18-point verification).
D · Clearance authority — node approves its own partners and operators. No sovereign sign-off required for individual deals.
E · Brand independence — sovereign name never appears in customer-facing materials. Truth Ledger entries remain sovereign-issued, but reference the node, not CircularOS.
F · Territory rights — exclusive or non-exclusive geographic / sector territory negotiated per node.
G · Revenue split — sovereign takes a percentage of node subscription revenue. Indicative 15% – 25%; node keeps the rest plus all per-tonne dPRN economics under whichever model their downstream partners run.

§3 · Qualification & Process

  1. Enquiry — application for Sovereign Node status (invitation-preferred; open application accepted).
  2. Qualification floor — minimum 100 verified tonnes moved through Standard 50/50 or any Subscription White-Label tier. Track record is non-negotiable.
  3. Setup fee paid — significant, not trivial. £25,000 – £75,000 indicative range, scaled to territory size and sector. Faith-backed deferred terms available case-by-case.
  4. Sovereign Node deployed — Gateway #28 activated. Branded portal stack provisioned.
  5. Training — how to deploy white-labels, manage subscriptions, set clearance, run the verification stack.
  6. Launch — first downstream white-label sold under the node's brand.
  7. Royalty cycle — monthly remittance: % of node subscription revenue + Covenant routing remains in place across all downstream activity.

§4 · The Prowess (What Sovereign Does NOT Do)

⊘ Sovereign does not manage the node's partners — the node does.
⊘ Sovereign does not set the node's prices — the node does (within Covenant floors).
⊘ Sovereign does not approve the node's white-labels — the node does.
⊘ Sovereign does not handle the node's customer support — the node does.
⊘ Sovereign does not appear on the node's marketing — the node owns the brand.
What sovereign does: mints the dPRN, routes the Covenant, runs the Truth Ledger, collects the royalty, holds the protocol. That's it. That's the franchise model.

§5 · Sealed Constants The Node Cannot Bend

A · dPRN value remains £450/tonne. Node cannot inflate or discount.
B · Covenant remains 7% routed to Fully Nourished CIC. Non-negotiable.
C · 18-point verification remains mandatory on every transaction. No "verification-lite" tier.
D · Carrot supplier-facing floor remains £200 (where applicable). Node cannot run a discount Carrot.
E · Truth Ledger entries are sovereign-issued and immutable. Nodes cannot self-mint or backdate.
F · Sub-white-label fees collected by the node are subject to the same royalty split — no off-book sub-tiers.
The node has freedom within the covenant — never outside it.

§6 · Revocation Terms

A Sovereign Node licence is revoked if the node:
⊘ Breaks any sealed constant in §5
⊘ Fails to remit royalty for two consecutive months
⊘ Sells dPRN below £450/tonne or runs a discount Carrot
⊘ Brings the system into disrepute (greenwashing, fraud, public hostility to the doctrine)
⊘ Sub-licenses outside the Covenant (off-book sub-tiers, undisclosed partners)
On revocation:
Licence revoked immediately. No refund of setup fee.
Existing dPRNs minted under the node remain valid — the prior work is honoured.
Downstream white-labels under the node revert to direct sovereign management or are wound down at sovereign discretion.
No appeal.

§7 · Why This Is The Most Powerful Tier

Standard 50/50 sells service. Subscription White-Label sells access. Sovereign Node sells sovereignty itself.

The buyer doesn't just rent the engine — they take over the thing. They build their own kingdom under your protocol. They put their face on it. They take the calls. They sign the deals. They manage the team.

You stop being a vendor. You become a covenant-holder. The node becomes a kingdom within the kingdom.

That is why the setup fee is significant. That is why the qualification floor is real. That is why the sealed constants are non-negotiable. The node is not buying a product — they are buying the right to extend the constitution.

§8 · How This Connects To The Wider Doctrine

MD-280 defines White-Label (single-gateway operators). MD-282 defines the level above — multi-gateway franchises with sub-licensing rights.
MD-281 defines Carrot White-Label. A Sovereign Node may sell Carrot White-Labels into their network and earn the royalty themselves (split with sovereign).
MD-279 (Bridge) says Doors × Roles = Self-Funding Army. Sovereign Nodes are the largest possible "door" — each one a self-funding franchise that pays back to the centre.
Gateway #28 in gateway_profiles.py is the technical anchor. MD-282 is its constitutional anchor.
The Sealed Line
"A white-label operates a gateway. A sovereign node operates a franchise.
They put their brand on it. They give their clearance. They manage their subscriptions.
You collect the royalty.
That's not a partnership. That's a kingdom within the kingdom."
— Jermaine Murphy · 19 April 2026 · MD-282 · SCP-2821
Continue Reading
CircularOS · Master Document 282 · The Sovereign Node Doctrine · sealed in the Sovereign Library
HANDSHAKE — witnesses
Handshake sealed.