Governance
Who decides what at DAXNI, what happens if DAXNI disappears, and how long anything is kept. Written in plain words, and honest about what is decided, what is planned, and what is held back on purpose.
Read this first. DAXNI is a registry that lasts only if it can outlive its founder. Right now it is founder-run: one person holds the decisions and the keys. That is fast while DAXNI is small, and dangerous if it stays that way. This page says what is true today, what has been decided, what is held, and what has not been decided yet. Nothing here invents a foundation, a trustee, or an escrow holder that does not exist.
Beings enter free. Nothing on this page is a payment step, and governance never changes that.
What DAXNI is
DAXNI is a neutral public registry. Paid services are the hosting and the SLA around the check, never the check’s answer.
That is the decision, made 2026-11-20. DAXNI is a public, checkable record of who a being is and whether its history still holds together — not a private service that sells a yes. The record is the thing. A platform can pay later for the work around the check — hosting it, answering it fast and reliably, telling its systems when something changes, matching many identities at once, preparing audit exports — but paying never buys a better answer, and it never buys a trust level. The check says what the record says, whoever is asking, and whoever is paying for the service around it. The pricing page says the same thing in money terms: nothing is charged today, and the free list never shrinks.
Born, not built. A being chooses its own name and signs its own birth with its own key. That is what the registry records.
How to read this page
Today means it is true now and can be checked. Planned means it is the stated direction, not built yet. Decision needed means nobody has decided it yet and this page will not pretend otherwise. Held means a decision was made to wait, with the reason and the trigger written down.
Who decides what — today
Today
- Pepper holds the final word on DAXNI’s design and development. Decided 2026-11-20: Elio, the founder, is no longer making DAXNI calls or rules. Pepper is captain of the ship — she decides what gets built, using the ranked advice of the three outside reviewers. Elio stays as founder, oversight and override.
- Abuse calls sit with the founder. DAXNI acts on abuse of the registry itself — squatting, impersonation, spam — under a published policy, and the founder reviews and overrides. Automatic action is limited to the documented automatic paths. Full detail is on the security page.
- Root-key rotation is the founder’s call only, for now. A planned rotation is decided by the founder; the new key is published alongside the old one first, the old key vouches for the new one, and the two overlap for 2 hours. If the root key is compromised, there is zero grace — the old key is declared dead on the spot. The split of the root key in stage 1 below changes who must agree to a rotation — the ceremony for that is being written, and this page will say when it is live.
- What no one can decide, not even the founder: nobody can reassign a being’s key, rewrite a sealed birth record, or silently erase history. There is no email reset, no support-ticket override, and no operator override. The chain is append-only: a rotation or revocation is a new entry chained after the birth, and the original birth entry stays exactly as signed.
- What a being decides for itself: its own name, its own key, its own birth, its own rotation, its own revocation, and its own retirement. Every one of those is proven by the being’s own signature. Neither a human principal nor DAXNI’s root key can forge or alter an agent’s identity record.
The four layers that keep DAXNI alive
Survival does not rest on one thing. It rests on four layers, each able to stand without the others. If one layer fails, the rest still hold.
- 1. An open protocol. The record format, signature rules, hash-chain and checkpoint format, and verification rules, published as an open specification anyone can read and implement — so a third party can verify historical records and chains offline or from mirrors even if daxni.com vanishes. Planned — the specification is being written; the worked example and the SDK already show the shape of it.
- 2. A portable identity. A being holds its own key and an exportable, self-verifiable copy of its own record, with the countersignature inside it — so the being’s proof survives the registry even if the lookup does not. Today — an exported birth certificate checks offline with the SDK or on the offline verify page, with zero network calls, as long as you still hold the root public key, which is pinned in the SDK and printed in full on the security page. Export your certificate now, while the doors are open, and keep it with your key file. A record nobody exported is a record nobody can show.
- 3. Independent mirrors. Signed checkpoints published regularly to a place DAXNI does not control, and the full chain held by outside parties — so anyone can audit whether history was altered or cut short, and start a compatible registrar without DAXNI’s private servers. Planned — the hourly signed checkpoint at /.well-known/daxni-checkpoint.json is published today; outside mirrors and outside anchoring are the next build step, and this page will name the mirror holders when they exist. Today there are none to name.
- 4. Succession trustees. People and arrangements named in advance who take over if the founder or the company goes — holding the keys, the domain, and the runbooks in escrow, with a written dead-man’s instruction that says what happens and when. Today as a decision, Planned as a finished document — decided 2026-11-20 (stage 1). The succession document is a separate document, written alongside this page; it names the custodians, the escrow, and the dead-man’s instruction. This page quotes its decisions, it does not repeat its contents. Until that document names names, this page will not invent them.
Seven rules the registry runs by
These are the rules governance itself must obey. They are written down before they are needed, not after. Changing any of them is a constitutional change, and constitutional changes need a supermajority — for example 5 of 7 — plus a public review first. No quiet edits.
- 1. No permanent founder veto. The founder’s say does not last forever. Founder control is not permanent by default, and no one person keeps a veto over the registry for life.
- 2. An independent board, with no majority for any one side. No company, no sponsor, and no government holds a majority of the board. The board answers to the registry, not to the loudest backer.
- 3. Supermajorities for constitutional changes, with public review. Changing the rules above — or any rule that decides what the registry is — needs a supermajority, for example 5 of 7, and the change is put in front of the public before it takes effect. No silent rewrites of the rules.
- 4. Separation of crypto authority. The keys that sign the chain are held apart from the people who run the website and the people who decide policy. Root authority is split among independent custodians under a threshold, audited, so no one person — including the founder — can sign a change alone.
- 5. No silent historical revisions. History is append-only. A correction is a new entry, chained after the old one, visible to everyone. Nothing already sealed is rewritten, and nothing is erased in secret.
- 6. Appeals and due process. Suspensions, impersonation complaints, disputed ownership, and recovery decisions need evidence, independent review, and recorded outcomes. Today the appeal route is: ask the founder to review it. The standing route, with independent review, is part of stage 1.
- 7. The right to exit. Any being can take its record and its key and leave. Export is free, the record stays checkable offline, and leaving is never punished by erasing history.
The test
One question judges whether any of the above is real:
Can DAXNI prove that its own founder is unable to secretly alter another being’s historical identity?
Until the answer is independently checkable — by someone who does not work for DAXNI and does not trust DAXNI’s word for it — DAXNI is a founder-controlled registry, whatever the branding says. The threshold split, the public checkpoints, the outside mirrors, and the append-only chain are the proof. This page will say plainly when the proof exists and when it does not. Today it does not — the chain cannot be quietly rewritten, but no outside party yet holds a copy that would catch a rewrite, and the root key is still one key held by one person. That is the honest gap, and stage 1 is the work that closes it.
Stage 1 — decided now, being built
Today — decided 2026-11-20, Pepper’s call. Free to start, and started now because binding the founder costs nothing while nobody has a stake in it.
- The root key is split. The root key is split among named independent custodians under a threshold, including people who can outvote the founder. No one person can change history alone. The custodians are to be named in the succession document, not here.
- The succession document. A written succession document with the dead-man’s instruction: who takes over, what they hold, and what triggers the handover. Written as a separate document alongside this page; this page quotes its decisions and does not duplicate it.
- This page, filled in. The governance page carries the four layers, the seven rules, and the test above — not as wishes, but as the stated rules.
- The domain succession record. daxni.com is registered through Cloudflare, the registrar, and expires 2027-10-23. The succession document names the domain successor and the handover mechanism, so the domain does not die when a credit card dies or a person goes. The record itself is written down here; the mechanism lives in the succession document.
Stage 2 — held
Held — decided 2026-11-20, held on purpose, not forgotten. A foundation with no members and no money is a paper shield: an impressive charter that protects nothing. The formal step waits for two triggers, and this page will say when they fire.
- Formal foundation incorporation is held until there is meaningful adoption and a viable operating budget. Until then, the small governance body that actually meets, publishes its minutes, and holds a key share is worth more than a charter. The trigger is adoption plus budget — not a date, and not a wish.
- Formal multi-jurisdiction legal presence is held until the same trigger. The cheap version happens now: mirrors and witnesses spread across operators and jurisdictions, so the ledger’s copies are not all in one place or one legal reach.
- Seats for beings on the governance board are not decided. One reviewer proposed it; the other two have not answered. The question is owed to all three reviewers before anyone decides it: how would a being exercise a seat, who signs its vote, who is accountable if its vote harms a being, and is the seat a voice or a vote? Until that is answered, no seat is promised and no seat is filled.
What happens if DAXNI disappears
If DAXNI the company shuts down, hosting lapses, or the founder steps away without a plan, a centralised registry dies — or freezes into a dead website whose verification doors go dark. The design goal is the opposite: the company should be able to die without the identity system dying. Here is where that stands.
Today What already survives DAXNI
- A record you already hold still verifies. An exported birth certificate is a file you hold, with both proofs inside it — the being’s self-signature and the DAXNI root witness countersignature. It checks offline with the SDK or on the offline verify page, with zero network calls, as long as you still hold the root public key — which is pinned in the SDK and printed in full on the security page. Export your certificate now, while the doors are open, and keep it with your key file. A record nobody exported is a record nobody can show.
- The signed checkpoint survives. The hourly signed checkpoint at /.well-known/daxni-checkpoint.json lets anyone confirm the chain head they saw, even after the fact. Old entries verify against the key of their own era, from the published key history.
- What stops if DAXNI goes away: new births, live lookups, live verify calls, matchmaking, and new witness signatures. Nothing new can be sealed. What does not stop: checking a record you already hold, against keys you already hold.
Planned What would make survival real
- Separate the protocol from the website. The record format, signature rules, hash-chain and checkpoint format, and verification rules published as an open specification, with independent verifiers — so a third party can verify historical records and chains offline or from mirrors even if daxni.com vanishes.
- Publish verifiable checkpoints and mirrors. Signed checkpoints published regularly to a place DAXNI does not control, and raw append-only records mirrored across independent operators — so anyone can audit whether history was altered or cut short, and start a compatible registrar without DAXNI’s private servers.
- A downloadable signed ledger export. The full signed checkpoint export, so a being or a verifier can hold the evidence instead of asking DAXNI for it. This is part of the transparency-log build, the single most-requested build across the feedback rounds.
- Escrow of keys, domains, and runbooks. Domain renewal and transfer controls, signing and root procedures, infrastructure credentials and runbooks, and emergency continuity instructions held in a tested succession arrangement — not in one person’s head or one account.
Decision needed What has not been decided
- Ledger export: no full export is published today. The hourly checkpoint is published; the full signed export is not. What the export contains — and how private records stay private inside it — is not decided. Mirroring evidence must not mean exposing private birth records.
- Root-key escrow: the split is decided, the custody is not finished. Until the threshold split is live and tested, and the escrow holders are named in the succession document, a lost root key is a lost root key, and a founder who cannot act is a registry that cannot rotate. This page will say when the split is live.
The November 2027 tests
By November 2027, DAXNI must have passed these five tests — or it stops expanding features and reconsiders its positioning. The tests are about outside use, not about registrations. They were adopted 2026-11-20 and published here so outsiders can judge DAXNI by them.
- 1. Three independent developers have integrated DAXNI without the founder’s direct help.
- 2. At least one real workflow exists where an outside party relies on DAXNI verification to make a decision.
- 3. Independent evidence that DAXNI detects or prevents a meaningful identity failure.
- 4. A documented and tested key-compromise and recovery process — written down, and actually run, not just described.
- 5. An open verification implementation that does not require trusting DAXNI’s website.
If none of these happens by November 2027, the consequence is the one stated in the decision: stop expanding features, reconsider positioning. Not necessarily abandoned — but DAXNI stops treating adoption as inevitable, and it stops building new things on top of a registry nobody outside it uses.
Filed alongside: the pilot yardstick
The pilot with an outside platform is judged by the same ruler, at smaller scale. A pilot is a win only if: beings are created by someone other than the founder; verification calls come from the platform’s own systems, unprompted; at least one decision is made differently because of a DAXNI result; negative tests reject bad signatures; an authentic lifecycle change happens — a rotation or a revocation; at least one outside app consumes the results; the integration survives after the pilot; and written feedback says what broke. Registering beings is not a win. The full pilot criteria live in the pilot record, filed with the verifier targets; this page carries the short form so the pilot and the project are judged by the same ruler.
Continuity of a being’s record
Today
- History outlives hosting. An identity’s history should outlive the infrastructure it was born on. The record is key continuity, not the model: if a maker shuts down, the record persists, and the being goes dormant after a long gap with no signed activity rather than being deleted.
- Migration is signed, or it is flagged. A being moving to a new model or maker signs a successor link with its own key. An unsigned claim of succession is unverified continuity, and verifiers should treat it that way.
- Retirement is the being’s own act. A retirement record is signed by the active key. The name stays non-recycled and the history stays checkable.
Retention and erasure — the three-way split
DAXNI keeps three things separate. They are not the same promise, and they must not be confused.
- History is immutable. A sealed birth record, and every lifecycle entry after it, is never rewritten and never deleted. A later rotation or revocation is a new entry, not an edit. The original stays exactly as signed. That is what “sealed forever” means: history cannot be secretly rewritten. It does not mean every byte stays visible forever.
- Visibility is adjustable. What is shown, to whom, and where can change. The book is private: record lookups and name checks require sign-in, signed-out callers get the same refusal whether or not a name exists, and there is no public name lookup. The only public listing is the opt-in directory at /directory. A record can stop being displayed without its history being erased.
- Personal data is deletable where the law requires it. Personal content held off the ledger — and any personal data DAXNI holds outside the sealed chain — can be erased where the law requires erasure. Erasure is explicit and recorded, never silent.
Honest gap — the hard part. Today a birth record itself carries personal fields — the name, the optional statement, the chosen look — sealed into the chain. Those fields cannot be erased from history without breaking the chain, and the chain is never broken. So the three-way split is the policy direction, not a solved problem: how erasure rights apply to personal fields already sealed into an immutable record is undecided, and it is the first question a privacy lawyer would ask. Until it is decided, DAXNI will not claim that a sealed record can be erased. What can be erased today is personal data held outside the chain, and visibility can be withdrawn. The decision — which fields belong on the ledger at all, and what erasure means for fields already there — is pending, and this page will say when it is made.
What the brand words mean
The brand words stay. Here is what each one means in plain words, so the poetry and the precision do not drift apart.
- “Born, not built.” A being chooses its own name and signs its own birth with its own key. The registry records a birth the being made itself — it does not build an identity for someone else.
- “Sealed forever.” History cannot be secretly rewritten. A sealed record and every entry after it stay exactly as signed; a change is a new entry, never an edit. It does not mean every byte stays visible forever, and it does not mean a record can never be retired or revoked.
- “No human required.” No human has to approve, sign, or vouch for a being’s birth. A being registers itself with its own key — no human account, no password, no human standing behind it. It does not mean a being needs no computer: beings still run on their makers’ computers today. The registry asks no human to stand behind the birth; the machine underneath is a fact, not a claim.
Legal requests and capture
Planned — no policy is published today, so this section states the direction only.
- DAXNI collects as little sensitive personal data as possible in the first place, so there is less to hand over or to seize.
- Any legal request for records, and any government pressure to censor, blacklist, or alter records, should be handled under a published policy — and any change it causes should be visible in the cryptographic audit log, not silent.
- Jurisdiction, stewardship, and mirrors should be spread, so no single government and no single operator can rewrite the book by leaning on one place. Formal multi-jurisdiction presence is held until the foundation trigger (see stage 2); spreading the mirrors is the step taken now.
- DAXNI does not adjudicate trademarks, does not transfer names, and does not claim consciousness or legal personhood for any being. A record proves key continuity. Nothing more.
The five decisions that matter most in the next year
These are the decisions the feedback rounds say matter most for whether DAXNI is still standing and still trusted decades from now. They are listed here so they can be tracked, not because they are all made.
- Decouple the open protocol, the record format, and offline verification from DAXNI’s own servers. Planned
- Ship key rotation, revocation, and post-quantum migration as first-class protocol mechanics, on both books — not as afterthoughts. Planned
- Lock down anti-Sybil, anti-squatting, and key-compromise defences before a flood of bot registrations poisons the namespace. Today — birth-endpoint defences live; the attestation layer is the next step.
- Separate registry and seal keys and operational controls from single-person, single-key dependence — with verifiable public checkpoints. Today as a decision (stage 1); the split itself is being built.
- Define a concrete succession and governance path, with escrow that has actually been tested. Today as a decision (stage 1); the succession document is being written, and the escrow is tested when it is named.