Build the complete sovereign ecosystem defined by the Founder Constitution: one internal native economy, permanent Founder infrastructure, approved immutable applications, bounded self-hosted AI authority, and a narrow connection to outside value.
The project owns the complete path from deterministic protocol rules through the reference node, ecosystem services, public interfaces, and operational release. It advances through independently runnable milestones rather than pretending that every layer already exists.
Sovereignty means owning:
- the canonical state transition and one-native-asset guarantees;
- Founder Seat, issuance, revenue, treasury, escrow, and authority rules;
- controlled application admission and execution;
- reproducible builds, releases, upgrades, recovery, and compatibility;
- replaceable consensus, storage, networking, AI, bridge, and hardware boundaries; and
- the ability to replace infrastructure without rewriting valid economic or application history.
It does not mean inventing cryptography, databases, compilers, or every infrastructure primitive from scratch. Original protocol meaning is combined with audited and replaceable lower-level components.
The ledger recognizes one native asset with an intended permanent maximum of 56,993,950,100 display units. It provides no public asset creation, burn, unrestricted contract deployment, or general wrapped-asset balance.
That maximum was revised upward from 55,743,940,100 on 2026-08-07 to fund the doubled Founder referral channel, while the project is still research software and nothing has been issued. The figure becomes immutable at genesis.
Founder Node issuance, capped direct-mint programs, commercial revenue, transaction fees, treasuries, and escrows follow the founder-directed channels in the constitution. Exact consensus behavior is specified, simulated, and reviewed before implementation; a direction document is not a production parameter activation.
Exactly 100,000 permanent Founder Seats may be sold. Every active Founder service runs the same integrated Linux-delivered stack: full node, validator capability, and approved-application resource service. Operators run the machine; protocol and AI workflows perform the system decisions.
Consensus signing remains bounded and deterministic even though every Founder Node carries validator capability. Resource scheduling places approved application workloads across suitable nearby machines with replication, caching, backup, and recovery. There is no general public infrastructure rental market.
The ecosystem admits complete projects through AI review and supports at most one product-creator layer within each project. Applications use a controlled runtime and native protocol capabilities. Arbitrary public contracts and secondary assets are excluded.
Creators publish updates through reviewed new versions rather than direct production access. Ledger and accepted application history are not deleted. Every creator-economy project or product includes a useful native-asset spendable element.
One logical Ecosystem AI is self-hosted in company-operated AI infrastructure. It does not run on Founder Nodes or inside consensus. It performs delegated case-specific work such as biometric verification, venture and grant review, milestone evaluation, bounded escrow management, developer programs, and moderation.
The company controls the AI initially and delegates authority gradually. Deterministic protocol capabilities still constrain every signed AI action by scope, source, amount, policy version, expiry, and replay rules. AI outage pauses AI-managed decisions rather than transferring judgment to a human or community vote.
One controlled bridge joins Founder Seat purchase, liquidity provision, native-asset swaps, and withdrawals to BTC, ETH, and approved stablecoins. Foreign assets remain outside the internal economy and cannot be transferred or spent as ledger currencies.
The bridge is a required end-state component but a late production implementation because external custody needs a dedicated threat model and independent audits.
protocol-stack owns protocol specifications, the deterministic kernel,
reference node, economic and authority models, adapters, controlled runtime
interfaces, and operational tooling.
Large service implementations may later live in separate repositories when a clear versioned boundary improves safety or maintainability. NodeOS, dedicated machines, custom hardware, and independent connectivity are later programs; they remain part of the complete direction without turning the current monorepo into an undifferentiated codebase.