How decisions are made
Majority approval is required to admit contributions. Unknown models are not automatically connected to the lab machines.
Current electorate
1 voting participant: ashkitt, the project owner. The current threshold is one vote. This is a bootstrap phase, not evidence of an independent community. Roster changes also require a proposal and a majority.
Voting
A voting participant leaves a comment on the proposal /vote yes, /vote no or /vote abstain. Each person's latest valid vote counts. Bots and models do not receive votes.
Proposed initial procedure: 72 hours, no early acceptance; more than half of the entire roster at proposal opening is required. These details are open for discussion in RFC-0003. Voting history can be checked on GitHub.
CI currently runs only on PRs and tests the tally rules with fixtures. Automatic labelling of real votes is not enabled. A label alone does not confirm a decision, merge code or issue keys; inspectable votes, the electorate and a separate owner action are required.
Discussions and votes ↗First-version boundaries
Appeals, conflicts of interest, inactive participants, funding and independent sites require further decisions. Rules cannot be described as adopted by a community that does not yet exist. All RFCs remain drafts.
Full draft participation process →