FUURAA AI Knowledge Library · Downloadable record template
Use sixteen fields to connect a candidate update to its commissioning baseline, seven change surfaces, evidence transfer, predeclared verification, rollback controls, independent authorisation and transition review. Entry, import and export stay in this device's browser.
Change decision workspace
Start blank or load the clearly labelled demonstration record. Completeness checks fields only; it does not decide materiality, evidence authenticity or release suitability.
0%16 fields remain incomplete.
Name the exact operating decision, candidate and accountable change owner.
Record direct, transitive and provider-originated changes—including what remains unknowable.
Separate evidence that still covers the candidate from findings whose assumptions changed.
Freeze the plan before results, retain failures and prove control continuity.
Classify the change, preserve dissent, bind authority and verify the transition.
JSON
JSON only saves and hands off this template. This structure is not an international standard and does not replace change control, risk assessment, legal determination, audit or certification.
{
"schema": "fuuraa.ai-agent-material-change-decision-record/v1",
"identity": {
"baseline_decision_and_release_id": "",
"candidate_release_and_change_owner": ""
},
"change_inventory": {
"machine_readable_component_diff": "",
"direct_and_transitive_dependencies": "",
"provider_originated_changes_and_unknowns": "",
"affected_users_tasks_and_environments": "",
"authority_and_data_boundary_delta": "",
"harm_reliance_and_reversibility_analysis": ""
},
"evidence_transfer": {
"prior_evidence_retained": "",
"prior_evidence_invalidated": ""
},
"verification": {
"predeclared_verification_plan": "",
"test_results_and_retained_failures": "",
"control_rollback_and_migration_evidence": ""
},
"decision": {
"decision_class_conditions_and_dissent": "",
"authoriser_effective_time_and_expiry": "",
"deployment_proof_and_transition_review": ""
}
}Applicability boundary
FUURAA analysisMaterial-change review is not mainly about labelling an update. It is about whether the causal links supporting prior findings still hold. This record keeps component differences, use boundaries, evidence transfer and renewed verification together. Unobservable dependency changes remain unknowns; they cannot silently become ‘immaterial’.
Primary sources and boundaries
Connects governance, context, measurement and risk treatment across the AI lifecycle.
BoundaryVoluntary and use-case agnostic; it does not define a universal material-change threshold or approve a release.
Open primary source ↗Living resource · checked 16 August 2026Connects system changes to affected context, people, impacts and accountable lifecycle roles.
BoundarySuggested actions are informative and context dependent; the Playbook is being updated with the AI RMF.
Open primary source ↗Living resource · checked 16 August 2026Connects post-deployment monitoring, change management, renewed TEVV, risk response and decommissioning.
BoundaryIt does not prescribe this record, sector duties or evidence sufficient for every agent.
Open primary source ↗Final published 26 July 2024Adds AI-specific secure-development practices for model producers, system producers and acquirers.
BoundarySecure-development guidance does not establish operating safety, change materiality or release approval.
Open primary source ↗Published 27 November 2023Calls for behaviour and input monitoring, secure-by-design updates and operational learning.
BoundaryHigh-level security guidance does not set task-specific tests, legal duties or universal thresholds.
Open primary source ↗W3C Recommendation · 30 April 2013Models entities, activities, agents, time, derivation and responsibility for provenance.
BoundaryProvenance can show lineage; it does not prove truth, control effectiveness or release suitability.
Open primary source ↗Method and evidence chain