Not a product page. Not a company homepage. The foundation on which everything else rests: the doctrine this architecture was built to express, and the proofs that make its claims verifiable.
The raw surface from which the sovereign individual interfaces with the timechain directly. No middlemen, no permission, no interference. No one can alter, remove or corrupt your entries. Ever.
Don't trust. Verify.
These are not policies. Not guidelines. Not a mission statement written for a website. They are the reasons everything exists, and the things that will not change.
Every ceremony, every record, every key, every year of the relationship exists to serve one outcome: a sovereign in full possession of their own identity, their own record, their own keys, beholden to no institution for access to what is theirs. That is not a selling point among others. It is the only point. Every other decision this architecture makes follows from this one.
These are not tiers. They are not versions of each other at different price points or commitment levels. They are three distinct instruments in service of one architecture. The compass does not point toward any of them as an improvement upon another. The sovereign decides which instrument, if any, to pick up.
The sovereign life itself. Every human being who chooses sovereign infrastructure is an Oak. The continuous record from the founding act to the Veil is the Oak record. Oak is the entry point for every sovereign, regardless of family status, age, or the season they are in when they arrive. Oak alone is a complete and sufficient sovereign path. Nothing is missing from a sovereign life that reaches for no other instrument.
The instrument an Oak picks up when they are ready to bring a new sovereign into existence. The founding act for a child's chain. Picked up when the moment arrives. Set down when the Sovereign Ascent completes. The new Oak stands. The parent's chain, which never stopped running, continues.
The ceremony of two Oaks choosing each other. A co-signed event. Each sovereign signs with their own key. The event appears permanently on both chains. Neither chain is merged. Neither sovereign holds the other's keys. Forge records the act of choosing, not the ongoing state of the union. What the union becomes over time is the sovereigns' own business.
These are not promises. They are technical and architectural facts that anyone can verify. A reader who wants to confirm them does not need to trust this document. They need only inspect the infrastructure.
Every sovereign identity in this architecture is generated by the sovereign themselves, on dedicated cryptographic hardware, in their own hands, at the moment of their founding act. Not issued by The Sovereign Path. Not accessible to The Sovereign Path. Not device-bound. This is technically true; the mathematics makes it true, not a contract.
Where a parent holds a custodial key on behalf of a child, that key is held by the parent across the full custody window and never leaves their hardware. The child's sovereign identity is generated by the child at the Sovereign Ascent, on their own hardware, in their own hands, for the first time. No institution issues this identity. The act of generation is the issuance.
Every signed event is broadcast simultaneously to three independent relay tiers: the company relay, an independent foundation relay stewarded outside company control, and a set of public Nostr relays. The record does not require a subscription to remain intact. The relationship between a sovereign and The Sovereign Path may end. The record does not.
If the company relay goes dark: the record remains on the foundation relay and the public relays. If all three tiers were somehow lost: the Bitcoin timechain retains the cryptographic anchor of every ceremony event, permanently, without any party's cooperation.
The child accepts or declines. If they accept, they generate their own keypair and co-sign the ascent event. That dual signature (the parent's genesis key signing for the last time, the child's new key signing for the first time) is anchored to Bitcoin. Permanent. Unalterable. On the public record.
If they decline: the record remains intact on public permissionless infrastructure. The child can find it, read it, and verify it at any point in their life, without involving anyone, without a subscription, without anyone's permission. Both outcomes honour the sovereignty claim. Neither requires the company.
Every record created by this architecture is verifiable by anyone, on public infrastructure, using only the sovereign's public key, generated at their own Founding Act. The instructions for doing this require no account, no login, and no contact with The Sovereign Path.
The code that constructs, signs, and verifies every record under this architecture is publicly available. Anyone can read it, audit it, and run it independently. There is no proprietary layer that must be trusted. The claims are either structurally true or they are not. The code is the proof.
The Sovereign Path occupies a category that does not yet have a name. Understanding what it is requires understanding what it is not.
The Sovereign Path does not offer content, community, expert advice, or curated developmental programmes. It is infrastructure. The record belongs to the sovereign. There is no engagement loop, no metric that matters except the completeness of the record across the life it was built for. The app is the instrument. The record is the product.
The instruments are priced at the work they require. No more. The scarcity in Legacy Genesis is architecturally real. Twelve families a year is a delivery constraint, not a positioning decision. Any sovereign who has reached the conviction this architecture requires can reach the instruments. That is the complete intent, and the complete justification for the prices set.
The Sovereign Path has no data business. No analytics layer. No advertising surface. No interest in what it holds beyond its obligation to the record. The record belongs to the sovereign. The keys are held by the sovereign. This is technically true, not a privacy policy statement. The architecture makes it true. The moment the company's commercial model requires the record it holds to be worth something to a third party, the sovereignty claim is false. This constraint does not bend at scale.
The Sovereign Path does not seek adherents. It does not build community around its philosophy. It does not publish manifestos or ask to be agreed with. It is a commercial architecture built to solve a specific problem, at a specific moment in the history of the technology, by people who understood both the philosophy and the engineering. The sovereigns who choose it have not joined something. They have made a sovereign act for themselves, or for a specific life they are responsible for. That act is private. That is the point.
Bitcoin is the infrastructure, not the identity. The timechain is the ledger that holds the record permanently outside institutional control. The Sovereign Path is not a token, not a wallet, not a speculation vehicle. It uses cryptographic permanence because cryptographic permanence is the only technology that can guarantee a record will exist in twenty years without institutional dependency. That is a technical decision, not an ideological one.
Every record created by The Sovereign Path is verifiable on public infrastructure using only the sovereign's PUBLIC KEY generated at their own Founding Act. No account. No login. No contact with The Sovereign Path.
Every event in the sovereign's record is signed with their key and broadcast to public Nostr relays. To retrieve the full record:
The ceremony events in every record are anchored to the Bitcoin timechain: the Founding Act, the Forge ceremony, the Sovereign Ascent, and the Veil. Each anchor embeds the cryptographic hash of the corresponding Nostr event permanently into a Bitcoin transaction.
No proof file. No intermediary. The transaction is the proof.
→ mempool.spaceEvery signed event can be re-broadcast to any Nostr relay: one you run, one you trust, or the public relay network. The record is portable because the events are signed by the sovereign's keys, not the company's. Migration tools are included in the ceremony package.
→ Self-hosting guide