Proposed
Pair open release with synthesis and exploit screening upgrades
If the model is public, the complementary controls must get stricter, not looser.
No compiled flow or public database names this control yet.
Who should own it
Synthesis providers and CERTs
Regulators
How quickly it can land
Months
A planned program, one to two quarters.
Expedited implementation
2 months
60 calendar days with a crash team
Normal implementation
6 months
180 calendar days as a planned program
Risk this mitigates
19Given that capable weights can be copied, fine-tuned, and mirrored faster than any lab can recall them, including models that help with cyber and biological tasks, there is a possibility of a high-capability checkpoint living permanently outside any access-control regime resulting in every other high-consequence scenario on this register becoming available to actors who will never see a safety team.
Residual composite 19 · still above the threshold
Effect if implemented
Applied to every failure scenario on that risk, then re-ranked. Axes are clamped at 1.
- Likelihood
- −0
- Consequence
- −1
- Urgency
- −0