| White-Label (MD-280) | Sovereign Node (MD-282) | |
|---|---|---|
| They operate | A single gateway | Multiple gateways |
| They brand | Their logo on your portal | Their entire system |
| They control | Their operations | Their partners, their subscriptions, their clearance |
| They pay | Subscription + revenue share | Setup fee + % of their subscriptions + (optional) equity |
| They become | A partner | A franchise |
| Sovereign visibility to end-customer | "Powered by CircularOS" footer (optional) | None — sovereign brand never appears |
| Approval authority | Sovereign approves their counterparties | Node approves its own counterparties (under the Covenant) |
gateway_profiles.py. Activates Sovereign Node Deployment.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.
gateway_profiles.py is the technical anchor. MD-282 is its constitutional anchor."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."