What is delivered
One completed assembly cycle in federation/assemblies/, run end to end against a delivery that has already happened — not a hypothetical one.
Open the cycle as an issue, claim the delivery, draft the report from the template, hold the seven-day window, record the tally, merge. The procedure is DAF-001 §4.
The specification of the DAF federation itself is a candidate: it was declared in a public issue, its result is inspectable, and it closed.
Why it is needed
The rules are written and nothing has ever been run through them. Quorum at 30% of active points, one point per function, a bonus per function on module completion — these are starting values that no use has validated. The first assembly is the cheapest possible way to find out which of them are wrong, and it costs nothing but the time to hold it.
Running it against real work also settles the awkward first question honestly: the founding steward holds a majority by construction, because the steward did the work. Better to have that visible in a real ledger than described in a document.
Where to start
DAF-000 §3.1 for what counts as delivered, DAF-001 §4 for the cycle, and the three templates in federation/.
Expect the templates to be wrong somewhere. The last section of the assembly report exists for exactly that — write down what the rules cost to operate, so the next revision argues with evidence.
This is an open function: small enough for one person to finish, defined enough that the result composes with the rest. Claim it in this thread before starting so two people do not carry the same function, and deliver through a pull request to master. It appears on the board at https://drayker.org/#org/fn
What is delivered
One completed assembly cycle in
federation/assemblies/, run end to end against a delivery that has already happened — not a hypothetical one.Open the cycle as an issue, claim the delivery, draft the report from the template, hold the seven-day window, record the tally, merge. The procedure is DAF-001 §4.
The specification of the DAF federation itself is a candidate: it was declared in a public issue, its result is inspectable, and it closed.
Why it is needed
The rules are written and nothing has ever been run through them. Quorum at 30% of active points, one point per function, a bonus per function on module completion — these are starting values that no use has validated. The first assembly is the cheapest possible way to find out which of them are wrong, and it costs nothing but the time to hold it.
Running it against real work also settles the awkward first question honestly: the founding steward holds a majority by construction, because the steward did the work. Better to have that visible in a real ledger than described in a document.
Where to start
DAF-000 §3.1 for what counts as delivered, DAF-001 §4 for the cycle, and the three templates in
federation/.Expect the templates to be wrong somewhere. The last section of the assembly report exists for exactly that — write down what the rules cost to operate, so the next revision argues with evidence.
This is an open function: small enough for one person to finish, defined enough that the result composes with the rest. Claim it in this thread before starting so two people do not carry the same function, and deliver through a pull request to
master. It appears on the board at https://drayker.org/#org/fn