Strong leadership, integrity checks, competence accountability. The constraints are written down, and the founder is inside them.
Eight layers, L0 to L7. The constitution sits above the founder. Each layer below carries a defined mandate, not discretion.
The highest constraint. It defines the non-votable items and the bounds on every waterfall parameter.
Fiduciary duty and oversight. The board guards the constitution, not the roadmap.
A 100-seat governance body. It holds the votes that constrain the founder.
Commander. Strategy and final coordination, inside the bounds the layers above set.
Daily execution and external delivery against the agreed strategy.
Structured task execution. Every action retains a Proof-of-Behavior record.
Regional and track coordination, connecting the network to local ground.
Professional service and basic participation. The broad base of the stack.
We do not hide that this is founder-led. The checks split in two: integrity can trigger removal; competence can trigger mandatory review.
The founder can be removed, but only through three gates clearing at once. The bar is deliberately near-absolute.
Triggers are limited to criminal conviction, medical incapacity, or financial fraud.
Sustained underperformance does not remove the founder. It forces a strategic review in the open, with a remediation plan.
This closes the gap left when only criminal conduct can act as a backstop.
Think Vitalik to the Ethereum Foundation: removable in theory, irreplaceable in practice. The competence check ensures irreplaceable does not mean unaccountable.
Six items sit outside majority rule. No motion, however large the majority, can override them.
A node's core privacy rights cannot be violated by majority vote.
Anti-money-laundering and compliance enforcement cannot be bypassed.
A formed Proof-of-Behavior record cannot be altered after the fact.
A signed legal agreement cannot be unilaterally breached.
An emergency motion that harms absent minority nodes cannot pass.
A short-term payout that damages long-term sustainability cannot pass.
The stack, the thresholds, and the non-votable items are public. Review the system boundary before any participation request.
