Designing for adaptation: Static and dynamic robustness in policy‐making
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Abstract Policy tools are chosen and deployed in the expectation that they will continue to work effectively over extended periods of time. This is a tall expectation to meet, given that the nature of policy problems and their contexts change constantly. To continue to operate effectively in the face of these changes and respond to policy feedback from policy actors and outputs, policy mixes must be robust. This robustness is of two types: static robustness in which policy means adapt while policy goals remain unchanged, and dynamic robustness in which both goals and tools change. The first equates robustness with resilience—that is, the ability to bounce back to a previous state and attain original goals in altered contexts caused by some change in internal or external conditions. The second, however, is more complex as it can involve changes in aspects of policy goals as well as means in order to allow policies to adapt more broadly by altering their form in response to changing circumstances. This second type of “dynamic robustness” focuses attention on the need for agility and upon the requisites for the creation of policy designs which allow for substantive changes in form as well as state. The article lays out these concepts and their interrelationships and the kinds of procedural and other tools involved in achieving either. It illustrates their features and differences using examples from different sectoral cases.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it