Use this checklist when changing protocol, data loading, credit assignment, evaluation, or paper-facing scripts.
load_task()exposestrain_datasetsandeval_suitesin a form directly consumable byload_task_datasets().- Local dataset paths resolve correctly even when the current working directory is not the repo root.
- Eval suite names propagate unchanged into dataset
datasourcenames. - Fixture tasks under
tests/fixtures/tasks/still load successfully.
RoleGraphstill rejects duplicate names, missing dependencies, and cycles.- Prompt rendering still supports
{question},{context}, and prior role outputs without raising on missing keys. - The paper-default
Reasoner -> Actorpath remains intact inconfigs/tasks/*.yamlandconfigs/roles/**/*.json.
- The paper-facing C3 path remains centered on
openrlhf/trainer/ppo_utils/experience_maker.pyplusc3/credit/*. c3/baselines/group_baseline.pyremains documented as a fallback path, not the primary implementation.- Changes to
marl_algorithm=autobehavior are intentional and documented. pytest -q tests/mechanism/test_credit_mechanism.pypasses (LOO and full-mean advantages match the hand-derived values on the paper's fanout).
MathEnvandCodeEnvreward entrypoints remain compatible with the rollout metadata contract.main_results.pystill aggregates by the expected benchmark names, which are the main-table suites since the evaluation protocol of 2026-09-15:- math:
MATH500,Minerva-Math,AMC23,AIME24,AIME25 - code:
MBPP-test,MBPP+ - math appendix, reported apart from the main table:
GSM8K-test,CMATH-test - the reported
AIMEcolumn isAIME24andAIME25merged, the same entryscripts/70_rebuild/final_eval.pywrites
- math:
- Analysis bucket metadata remains compatible with
c3/analysis/metrics.pyandc3/reporting/analysis_results.py.
pytest -q testspasses.- Fixture-based smoke passes for both math and code tasks.
pytest -q tests/contract/test_release_surface.pypasses.bash scripts/90_audit/pre_release.shpasses.bash scripts/90_audit/release_gate.shpasses on a CPU machine.
- If the implementation path changed, update
docs/10_code_map.md. - If the paper-facing mapping changed, update
docs/20_implementation_audit.md. - If release behavior changed, update
README.md,docs/00_getting_started.md, anddocs/50_release_policy.md.