ProposedOn the path to acceptable
Capability thresholds that cannot be open-released
Below the line, open is a default. Above it, weights stay behind an access regime.
No compiled flow or public database names this control yet.
Who should own it
Labs and export-control authorities
Regulators
How quickly it can land
Months
A planned program, one to two quarters.
Expedited implementation
3 months
90 calendar days with a crash team
Normal implementation
9 months
270 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
- −1
- Consequence
- −1
- Urgency
- −1