Reference

For a justified machine-executed action, preserve the link from decision/version to approval, exact action, platform receipt, exposure, outcome and evidence. Bind approval to the material action fields. Recheck current permission, destination, state and cumulative limits before execution. An indeterminate platform result requires a state query and reconciliation before retry; a successful API response is not necessarily a delivered customer outcome. Keep manual or native fallback and a named restart authority. [SYS §§15,20–22,25; AGT §24 and contract pack]

For a justified predictor, record objective, target, horizon, population, training/holdout periods, leakage tests, feature provenance, calibration, missingness, relevant subgroup performance, version, owner, drift trigger and fallback. For uplift, add identification and treatment-policy evaluation. For generated summaries, verify source fidelity and missed/contradictory evidence. These are different evaluations.

The specialist sources retain detailed API schemas, identity patterns, statistical methods and security controls. Consult SYS §§23–28 and AGT’s Implementation Contract Pack only after the chosen Play requires those capabilities. The five working artefacts remain the operational record of what was actually configured.