Weight follows delivered work.
DAF is the organizational half of Drayker: how decisions and resources move when there is no head office to move them. A point records one delivered function. It cannot be appointed, it cannot be bought, it cannot be transferred, and it does not decay — influence moves only as other people deliver.
The record is empty, and that is the honest state rather than a placeholder. The structure exists so the first delivery has somewhere to be written down. The federation begins at the first assembly that records real work — not at the commit that created the folders.
Which means the first function is unclaimed and the door is wider than it will ever be again: open the cycle, claim a delivery that already happened, and take it through the procedure to see where it breaks.
How a finished piece of work becomes voting weight.
Six steps, and no discretion anywhere in them. Each one answers to a written rule, each rule is a line you can open and argue with, and each step is an ordinary thing on the platform the federation already runs on.
{{ dafStepOpen.b }}
From the first draft to the substrate that will carry it.
The federation was designed for a chain three times before it ran anywhere: Aragon on Ethereum, then DAOHaus on Optimism, then canisters on ICP. Each was abandoned before deployment — not because of the design, but because a chain demands funding, tokenomics and an audience before the federation has produced a single recorded decision. So Phase 0 inverts the order: run the rules first on infrastructure that already exists and already works.
Aragon on Ethereum, DAOHaus on Optimism, canisters on ICP. Each draft taught the design something and each was abandoned before running, for the same reason: the substrate cost more than the federation had produced.
Git history is the ledger, points are integers recomputable from history, votes are declared in the open, no treasury is held. The smallest thing that is a real federation rather than a description of one. It buys none of the guarantees a chain buys — and says so plainly.
ICP (Internet Computer Protocol) is the stated direction, on conditions: migrate when there is value whose guarantee justifies a chain, and carry a real history into the migration instead of a whitepaper. Deliberately deferred: the transferable instrument, councils, automated function evaluation, anonymous participation.
The right-hand column of the phase map is not a roadmap and carries no dates. It is a record of what was deliberately left out, so that Phase 0 is not mistaken for the whole design and the rest is not mistaken for work in progress. Detail in DAF-001.
A constitution short enough to be read before it is obeyed.
DAF-000 says what has to be true, independent of any platform. DAF-001 says how it runs today, on a repository. Both are drafts, open to argument, and neither overrides GOVERNANCE.md — the governance actually in force during the founding phase. Where they disagree, that file wins.
One point per function. One more per function if the whole thing works.
Stop delivering while forty more functions land elsewhere and that share becomes {{ calcLater }}. Points never decay and are never taken back for inactivity — the share falls because other people worked. That is the whole mechanism by which founding weight is meant to disperse.
Thirty per cent has to look at it. Then half of them have to agree.
Move the weights and watch the rule behave. The threshold is deliberately a participation floor rather than an approval floor — below it nothing passes, whatever the split.
What this MVP holds, and what was deliberately left out.
The right-hand column is not a roadmap and carries no dates. It is a record of what Phase 0 does not attempt, so that the small thing running now is not mistaken for the whole design, and the rest is not mistaken for work in progress.
A record, and one thing you finished.
No fee and no invitation. A participant or unit submits a record and delivers a first function; the record and the first award are accepted in the same assembly. Both forms below compose the artifact and hand it to you on GitHub — nothing is transmitted from this page, which has nowhere to transmit to.
A record states only what the federation needs in order to count your vote and find your work. Internal governance, member lists and finances stay with the unit. Send it in the same pull request that claims your first delivered function — a record without a delivery is not a unit yet.
A claim is public and can be contested by anyone in its thread. That argument is the review — there is no committee behind it. All three conditions have to hold before this form will let you post.
There is no committee. A claim is checked by whoever reads it, in its own thread, which means contesting one is ordinary participation rather than an accusation — and doing it well is itself work the federation depends on.
Say which of the three conditions fails and show why with links. A contest without evidence is an opinion, and it costs the thread more than it gives.
One cycle a month. Seven days to argue with it.
A cycle opens as an issue and closes as a merged report. Every award and every penalty in it names the delivery it answers to, and anyone can recompute the ledger from the history. The report is the record: anything decided elsewhere did not happen.
Two artifacts, in order: the cycle issue that collects the claims, then the report as a pull request with the awards written out. Running an assembly is itself a function, and it earns a point like any other.
A vote is a single comment on the assembly pull request, in a fixed format so it can be found and counted mechanically. Anything else in the comment is discussion. Your last comment of this form is the one that counts — so you can change your vote by voting again before the window closes.
The same arithmetic as tools/tally.js, run here in your browser: read the comments on an assembly pull request, keep each holder's last vote, weigh it by the ledger. Nothing is submitted — the official table is still written by a person into the report, which is what Phase 0 buys and all it buys.
LEDGER.md as it stands now. A real count weighs it at the previous assembly — tally.js --ledger-ref does that, and it is what keeps the awards under vote from changing the votes that approve them.VOTE: then AS:, each on its own line — that strictness is what makes counting mechanical instead of interpretive.What the record looks like once it is running.
Every holder, delivery, penalty and figure below is invented, and describes no real person, unit or work. It is here because the shape of the record is easier to learn from a filled page than from a template — and because the first real one has to be written by someone who has seen one.
{{ ex.where }}
{{ ex.change }}
This section is the reason the rules are drafts. Parameters that did not behave as expected, procedures that cost more than they were worth, gaps that only showed up in use — the assembly is where they get named, and a rule nobody argued with is a rule nobody used.
Ask only where there is no other way.
The federation is funded by grants, donations and side projects, it is non-profit, and it holds no reserve it is not prepared to justify. Support is a last resort — published on purpose, because a federation that treats shared resources as a first resort stops being able to fund anything that matters.
The rule is enforceable rather than decorative: a request that does not say what was tried first is returned unjudged. Funding is granted one function at a time, each grant evaluated against the evidence of the last — and undelivered work does not merely fail to earn points, it degrades every proposal that references it.
The parameters are written. No use has tested them yet.
Where a rule is unspecified the federation says so, rather than filling the gap with practice — undocumented custom is how a structure without an owner acquires one. What follows is the whole of it: four things the constitution does not settle, five things this substrate does not buy, and four conditions that would end Phase 0. They are open functions, not oversights.
A repository is not a chain, and the difference is stated rather than hidden.
These are limits of the substrate, not defects in the design. They are the argument for a later phase — and the reason to know exactly what the federation is worth before paying for one.
None of these is reached by adding features. Each is reached by the federation actually working — which is why the migration is a consequence of Phase 0 succeeding, not a prerequisite for starting it.
Everything the federation has decided, and the arithmetic behind it.
Read from federation/ at master — the ledger, the unit records and every assembly report, parsed from the files themselves. The audit tab sums the reports and checks the ledger against them, because a decision that cannot be recomputed from the public record did not happen.
This check runs in your browser against the files at master — nothing here is taken on trust from the site. Where the two disagree the reports win, because the ledger is only a summary of them, and the correction belongs in an issue rather than in a quiet edit.