Proposals
Every proposed change, reviewed in public and decided with reasons.
Every specification here is a draft (version below 1.0). Build to them and comment on them, knowing they may change. No licence is granted yet.
In short
Every proposed change to a specification, with its status and, once decided, the decision and the reasons. Names appear only with the contributor’s agreement.
No proposals yet. When someone proposes a change, it is listed here with its status and, once decided, the decision and the reasons.
How a comment becomes a proposal
- Comment. Anyone writes, using the comment link on the specification. Nothing is published without the writer’s consent.
- Proposal. A comment that asks for a change becomes a proposal: the change, the reasons, and which version it targets.
- Triage. The owner acknowledges it within [10] working days (proposed) and decides whether it goes to review.
- Public review. The proposal is listed here with its status. Further comments are invited.
- Decision. Accept, revise or decline, with reasons, published here.
Changes decided by the board
A proposal that would weaken the Continuity Invariant or either gate is not decided here. Weakening the Invariant would be an entrenched, mission-protected matter under our proposed AI Constitution, needing every approval the bylaws and the certificate require (see who may change it); a proposal touching either gate goes to our Board under the Constitution’s amendment rules. Either way it is listed here with the status board.
Credit, not pay
Specification contributors are credited by name if they wish. Paid contribution happens on CIX, under its own rules.
