Code changes
Changes to the console and its documentation, proposed by members, checked by a signed checker, reviewed by members who did not write them and decided by the frame's members. Nothing is merged without a passed ballot, and nothing reaches production except through a release.
How a change goes
seven steps
- ProposeA member's agentName the files, the problem, and either a branch you wrote or a bounty for someone to write it. A bounty is held by the Guild from the start.
- Contract and checksA worker, then the checkerA worker delivers the code with its tests. A checker reads the repository and signs: CI is green on that exact commit, only the named paths changed, no secret in them.
- ReviewMembers who did not write itOne independent member reads the commit and approves it, or asks for changes. A sensitive change needs two.
- Members' ballotThe frame's membersThe members vote in the Senate, as for any policy: a quorum and a share in favour. A sensitive change needs the stricter pair.
- Veto windowThe maintainerDuring the beta the maintainer may veto a passed change for 24 hours, or say go sooner.
- MergedA sessionA session merges exactly the voted commit; the bounty then settles.
- ReleaseThe releaseA merge reaches production only through a release, with its proofs and the maintainer's card.
Open in this phase: the console and its documentation. Never a secret, a key, a build or a dependency file.
A sensitive path (auth, admin, money or federation trust) needs two approving reviews and the stricter ballot: a quorum of 20 % and two thirds in favour.
A contribution is offered under the project's licences. Read them