THE PLATFORM
The committee
The committee is the platform's accountability: every decision that shapes
the catalogue traces back to a named person on the
committee page. Members hold the committee role. Platform administrators can take the same actions but are not seats on the committee — the page lists the seated members, not the powers.
What the committee decides
| decision | how |
|---|---|
| a proposed kernel enters the catalogue | review: claim, notes, approve or return |
| a specification is published | review of the signature, correctness statement and bundle |
| a revision to published content | same review, against the live version |
| an image joins the catalogue | a committee member's own proposal publishes at once; anyone else's waits for one to publish it |
| a contested benchmark | arbitration on the run's recorded facts — code, machine, image, bundle |
Every seat has an equal vote. There is no chair and no casting vote.
What the committee does not decide
Verdicts. A benchmark's outcome comes from the specification's bundle and its declared bar, applied mechanically by the platform — the committee reviews the examination, never the grades. Standings compute themselves.
The review trail
A review is claimed by one member, argued in notes the author can answer, and closed with a decision that stays on the record. Decided reviews are counted on the committee page; the reasoning stays attached to the kernel or specification it concerned.
Joining
Open to anyone with published work on the platform or a public record in the field. Apply from the committee page — say who you are and what you have built. A seat is personal: it does not transfer with employment, and no organisation holds more than the people it actually seats.