From divided authority to accountable power.
The architecture is promising; the constitution is not finished. This page records what this Foundation repository can repair, what belongs in the protocol repository, and what must be proven before money or decentralization claims are allowed.
01
Decisions made here
One proposal, generated from one policy file. Still non-operational and subject to Estonian legal review.
5%
Maximum ordinary annual endowment appropriation from the trailing 12 quarter-end average.
7%
Maximum exceptional appropriation for one financial year.
7/9
Exceptional approval, including at least 4 non-sponsor directors: 2 Ecosystem and 2 Public-Interest Directors. A conflicted director cannot participate or count toward quorum.
The pinned upstream whitepaper and sponsor profile currently disagree with each other and with their own example record. Those pages carry visible consistency warnings. The Foundation will not accept money until the authoritative drafts and final legal documents agree.
02
Foundation-owned work
Governance and accountability this institution must supply rather than delegate to protocol prose.
Constitutional consistency
Generate numeric claims from one machine-readable policy; publish document precedence; fail closed on conflicts.
All nine directors
Give Sponsor, Ecosystem, and Public-Interest Directors separate electorates, plus a time-bounded founding transition—not only a donor electorate.
Money and custody
Publish the founding budget, custody matrix, investment policy, gift terms, conflicts, complaints, and reports before conversion.
Concentration
Disclose common control and material infrastructure in grants, procurement, catalogs, and Foundation-funded defaults.
Incident ownership
Every grant and service agreement names an incident coordinator and one complaint path. Modularity cannot become a blame maze.
Legal adoption
The MTÜ articles and adopted policies—not this website—must lawfully implement the proposal.
03
Protocol-owned work
The Foundation can fund and publish this work, but cannot pretend a website implements it.
One vocabulary
Canonical seat types, profile IDs, schema IDs, manifest envelopes, signatures, and revocation.
Identity continuity
Descriptor, capabilities, seat keys, rotation, revocation, recovery, and secure operator succession.
Exit tests
Full state export, third-party conformance, provider replacement, and governed notary migration.
Commercial constitution
Canonical offers and entitlements plus real billing-broker insolvency, complaint, audit, and provider-exit duties.
Route accountability
A named assembler or incident coordinator for composed failures, without giving it identity sovereignty.
Draft repair
Resolve the missing bank dependency, notary replacement conflict, and Foundation constants in `onym-system`.
04
Proof before claims
The test is whether the original operators can disappear without taking identity, relationships, or state with them.
- Import a non-default manifest and remove the default Discovery catalog.
- Use independently authored UI, relay, blob, read, and submission components.
- Export all local state and migrate a group under its actual governance rule.
- Rotate compromised operator and identity keys without silent rollback.
- Publish every failure, data loss, switching cost, control-group overlap, and responsible incident owner.
Until this drill passes, the honest description is “blueprint for replaceability,” not “decentralized institution.”
05
Activation gates
Any failed gate keeps the Foundation non-operational.
- Upstream and local money/vote rules agree
- MTÜ articles implement all three board classes and the transition
- Budget, custody, gift, investment, conflict, privacy, incident, complaint, and retention policies published
- Legal entity, lawful board, custody, and signature authority exist
- Every pledge is re-consented against the final terms
- Control-group and material-infrastructure concentration disclosed