Sources and record of changes

Sources, Review Status, and Record of Changes

1 Sources used to create this site

Source	Exact saved version used	Material used here
`SPRFMO/jmMSE`	`278c309888c03d241c0aa42967200351ffaa3b05`	Primary source: the ten CMP controls, seeded candidate runner, robustness selection, HCR implementations, repeatable MP43/MP44 tuning, and July presentation
`SPRFMO/scw17`	`0eb97c9c0329f5ec3338e3cf885f6e1f184c4780`	Secondary source: Papers 03, 04, 08, and 09 plus Quarto conventions
`output/jm_candidates.slick`	SHA-256 `6b17b0b0bb5483611f82f97c9d368dddcf2a69934ec2fd2bb110129b32685a8f`	Combined reference and robustness results for ten CMP comparison cases with six annual metrics, including VB/VB[2025] and VB/VB[MSY]

The current registry derives from jmMSE, not the SCW17 test table. It does not assert that MP29 or MP32 has been formally recommended or adopted. The eight additional CMPs are comparison cases, not advanced candidates. MP43 and MP44 retain the MP29 and MP32 structures but use a 20% maximum annual decrease and 15% maximum annual increase; their triggers were retuned before evaluation.

2 Information that must accompany each CMP

Every CMP version must link to:

the method used to calculate its indicator, harvest control rule, and catch allocation;
all parameter values and annual data requirements;
the exact saved version of jmMSE used for evaluation;
OM and robustness scenario definitions;
definitions of the performance measures and links to the saved results;
review findings and known limitations; and
the decision that changed its status.

3 Types of change

Class	Examples	Required review
Wording only	Spelling, navigation, or clearer background explanation	Documentation review
Same calculation, revised code	Software change shown to give the same answers	Code review plus a repeat-calculation test
Scientific	Parameter, index, window, HCR, constraint, allocation, or fallback change	Renewed scientific review and normally MSE evaluation
Status	Test to shortlist, recommendation, adoption, or retirement	Cited decision record

4 Work still needed

Confirm the formal working-group status and stable identifiers for MP29 and MP32.
Confirm whether MP43 and MP44 should remain annual-limit sensitivity cases or be considered in any later shortlist.
Reconcile the 100-iteration MP29/MP32 tuned triggers with the 500-iteration MP41/MP42 sensitivity values before approving a final version.
Archive the full jmMSE run objects alongside the published Slick file and its digital fingerprint.
Complete the required units, annual cutoffs, missing-data rules, rounding, and exceptional-circumstances provisions.
Add saved worked examples and automatic repeat-calculation checks.

--- title: "Sources and record of changes" --- {{< include ../_includes/sprfmo-banner.qmd >}} <div class="paper-title">Sources, Review Status, and Record of Changes</div> ## Sources used to create this site | Source | Exact saved version used | Material used here | |---|---|---| | `SPRFMO/jmMSE` | `278c309888c03d241c0aa42967200351ffaa3b05` | Primary source: the ten CMP controls, seeded candidate runner, robustness selection, HCR implementations, repeatable MP43/MP44 tuning, and July presentation | | `SPRFMO/scw17` | `0eb97c9c0329f5ec3338e3cf885f6e1f184c4780` | Secondary source: Papers 03, 04, 08, and 09 plus Quarto conventions | | `output/jm_candidates.slick` | SHA-256 `6b17b0b0bb5483611f82f97c9d368dddcf2a69934ec2fd2bb110129b32685a8f` | Combined reference and robustness results for ten CMP comparison cases with six annual metrics, including VB/VB[2025] and VB/VB[MSY] | The current registry derives from `jmMSE`, not the SCW17 test table. It does not assert that MP29 or MP32 has been formally recommended or adopted. The eight additional CMPs are comparison cases, not advanced candidates. MP43 and MP44 retain the MP29 and MP32 structures but use a 20% maximum annual decrease and 15% maximum annual increase; their triggers were retuned before evaluation. ## Information that must accompany each CMP Every CMP version must link to: - the method used to calculate its indicator, harvest control rule, and catch allocation; - all parameter values and annual data requirements; - the exact saved version of `jmMSE` used for evaluation; - OM and robustness scenario definitions; - definitions of the performance measures and links to the saved results; - review findings and known limitations; and - the decision that changed its status. ## Types of change | Class | Examples | Required review | |---|---|---| | Wording only | Spelling, navigation, or clearer background explanation | Documentation review | | Same calculation, revised code | Software change shown to give the same answers | Code review plus a repeat-calculation test | | Scientific | Parameter, index, window, HCR, constraint, allocation, or fallback change | Renewed scientific review and normally MSE evaluation | | Status | Test to shortlist, recommendation, adoption, or retirement | Cited decision record | ## Work still needed - Confirm the formal working-group status and stable identifiers for MP29 and MP32. - Confirm whether MP43 and MP44 should remain annual-limit sensitivity cases or be considered in any later shortlist. - Reconcile the 100-iteration MP29/MP32 tuned triggers with the 500-iteration MP41/MP42 sensitivity values before approving a final version. - Archive the full jmMSE run objects alongside the published Slick file and its digital fingerprint. - Complete the required units, annual cutoffs, missing-data rules, rounding, and exceptional-circumstances provisions. - Add saved worked examples and automatic repeat-calculation checks.