Waiting for approval

Changes to the product are built, tested and held here. Data keeps flowing: a wave of fetched trials is freshness and ships on its own.

How a change gets in

An agent finishes, and the gates pass: validate, typecheck, lint and the full test suite.
scripts/change-class.ts asks whether it touches the product or only the data.
If it touches the product, the chain refuses to deploy it and it is pushed as a pull request instead.
You merge the pull request. That is the approval, and the change ships on the next run.

This page is a reading surface, not a lock. The site is a static export with no server, so it is public like every other page and it holds nothing that is not. What actually protects the live site is that merging is yours, and that production deployment can be restricted to a branch only you merge. Both are settings in your accounts rather than code in this repository. See docs/PRODUCT-APPROVAL.md.

4 waiting

30 page titles named for the question the page answers
78 files · proposed 2026-09-28 · product/page-titles
Read it and merge to approve
/software/, the software of oncology, which answers issue 63
27 files · proposed 2026-09-28 · product/software-map
Read it and merge to approve
the top of a record page, all four asks as one pass
19 files · proposed 2026-09-28 · product/record-page-top
Read it and merge to approve
/v2/ shows the work instead of listing it
5 files · proposed 2026-09-28 · product/v2-shows-the-work
Read it and merge to approve