For everyone
The pipeline, as it runs right now
What is being verified, promoted and checked for you this very minute; how fast maintainers decide; who is building what, and what it costs. The same page for users, contributors and maintainers — only which buttons are live differs.
A living system
What each security feed contributes →Every three hours: packages are verified and promoted, five security feeds are matched against what every ring serves, and a confident fix does not wait for the soak.
stable; amber marks are advisories being matched against each ring. The dashed arc is the fast-track. The numbers are the pool's own.Nothing here is a promise: every line links to the run that produced it, and every decision carries a name. The whole journal →
Review throughput
How a decision is made →How fast new packages arrive and how fast maintainers decide. A wait is a queue, not a verdict.
Decisions per week 8 weeks
Arrivals vs decisions 8 weeks
Who is deciding on the record
Operations
read-only — approving and rolling back need the maintainer roleHow it runs
The factory in detail →One brain queues, workers claim with a lease, objects land on R2, rings are rendered and signed. Live numbers on the mechanism.
Review queue
Decisions and the audit →Evidence, not packages. Build by the project queues a rebuild on the review worker; approve publishes the project's build; reject sends a note back.
| # | Package | Arch | Built by | Evidence | Audit | Waiting | Decision |
|---|
The last two weeks
Every chart on the Status page →Pool jobs 7 days
Promotions 14 days
Health 14 days
Imports per day 14 days
Sync throughput last runs
Factory builds 14 days
Build tasks
leased first, then queued, then the most recent finished; three attempts, then failed| # | Package | Arch | Status | Reason | Worker | Took | Result |
|---|
Requested packages
Request one →Every package a contributor asked for — each request written once to the record and signed by the pool — and where it stands.
| Package | Project | Owner | Arches | Version · licence | Stage | Detail | Updated |
|---|
Rings and the journal
Ring history, diffs, rollback →| Status | What | Ring | Source / arch | Summary | Took | When |
|---|
Cost, in the open
Cloudflare, estimated every three hours from its analyticsD1 rows read and written are most of the bill. Estimated every three hours; the report warns from US$ …, the guard pauses the jobs that write at US$ …, the cap is US$ …; the daily report says why.
Help keep it running. The pool runs on one pocket: the brain on Cloudflare, one machine building for both architectures, and the agent tokens that draft and audit PKGBUILDs. More hardware means shorter queues; more tokens mean every build gets an audit.