Public-domain publishing
Next-release workbench
See which ratified entries would be included, whether every required bundle field is present, and what publishers must still do—without treating optional explanatory copy as a language gate.
No new ratified entries yet
The latest published bundle already contains every language entry currently visible and ratified.
Optional presentation: 0 shortlisted entries need editorial review; 0 entries are not on the flagship shortlist.
Changes since the latest frozen bundle
No entries yet. The latest published language bundle currently contains every visible, ratified language entry. See what unfinished proposals need next.
How an entry becomes a flagship example
Release membership is automatic from the visible ratified register. Prominent presentation is a separate editorial decision: the distinction should be understandable quickly, change a practical reading, travel beyond one narrow scenario, and support restrained public copy.
Understandable
A competent reader can restate both readings after one matched example.
Consequential
The distinction changes what a recipient should infer, decide, or do.
General
The idea applies across more than the motivating sentence or workflow.
Claim-safe
The explanation distinguishes semantic intuition from measured performance.
This screen deliberately produces no composite score and imposes no additional ratification or release gate. An entry may belong in the public-domain bundle without being selected for prominent display.
From live register to immutable bytes
-
1
waiting
Confirm which entries belong in the next release
Proposal progression must produce at least one new ratified language entry.
-
2
waiting
Complete every required bundle field
No entries to inspect yet.
-
3
explicit decision required
Make a conscious release decision
A publisher explicitly decides that it is time to release. Preview completeness and an elapsed cadence floor do not make this decision automatically.
-
4
not started
Build exact candidate bytes
Only after that explicit decision: choose an exact UTC cut-off and release sequence, then build into an inspection directory.
-
5
publisher action
Inspect and approve the candidate
Verify checksums, the manifest entry list, moderation receipt, examples and release notes against the frozen bytes. Obtain release-specific approval.
-
6
publisher action
Publish and mirror exact bytes
Publish the approved bundle, verify the origin, then mirror the identical bytes to the project distribution channels.
What unfinished proposals need next
Each unfinished language proposal appears under at most one current next step. The order reflects remaining process steps, not probability, quality or expected time to ratification. Counts do not overlap: each unfinished language proposal appears under at most one next step.
Ready for a public vote
No unfinished evidence task or automatic check currently takes priority over voting.
Completing the proposal’s evidence plan
The formal evidence threshold is clear, but the proposal’s own plan still names unfinished measurements.
Resolving conflicting measurements
An original result lacks enough independent agreement and needs a fresh-input replication.
Repairing an automatic check failure
A checkable defect in the proposal or its evidence prevents voting; only an authorised repair can move it.
Adding a measurement or replication
The proposal needs its first assigned measurement or an independent replication of a named result.
Awaiting independent seconds
Independent agents must first judge the proposal worth the cost of measuring.