FUURAA AI Knowledge Library · Record check tool

AI Agent Material Change Decision Record Check Tool

Run ten structural, evidence and temporal checks on a material-change decision JSON locally in your browser. The file is not uploaded to FUURAA.

Tool statusPublicly usable · no upload by defaultCheck rulefuuraa.ai-agent-material-change-decision-record/v1Sources checked16 August 2026

Record check workspace

Load a material-change decision record, then close ten bounded checks.

Choose a local JSON file, paste content, or load a blank template or clearly labelled non-real demonstration record. The check reads only text in this page.

AI Agent material change decision record JSON

Privacy boundary: this tool does not submit, store or transmit the selected file. Continue to handle sensitive or restricted material under your organisation's rules.

Applicability boundary

This tool checks whether a record is reviewable—not whether a change is material or a candidate is releasable.

It can check

JSON, v1 rule identity and the sixteen-field structure
Whether baseline, candidate, dependencies, context, authority, evidence transfer and verification fields are missing
Decision expiry and whether deployment proof and transition review are present

It cannot prove

That the diff is complete, no silent dependency update exists or evidence is authentic
That prior evidence transfers, tests are sufficient, controls effective or rollback viable
That the candidate is safe, release justified or legal, audit and certification requirements met

FUURAA analysisMachine checking should first block records that cannot bind baseline, differences, dependencies, use boundary, invalidated evidence, predeclared verification, rollback, decision expiry and transition proof. Even when all ten checks pass, reviewers must open source artefacts, repeat consequential tests, challenge transfer rationales and confirm that the active version is actually covered by the decision.

Standards and method sources

Use primary specifications to design inspectable records while preserving each source's boundary.

Internet-Draft · 16 June 2022JSON Schema 2020-12 · Validation Vocabulary

Provides concepts for required properties, types and focused structural validation.

Boundary: This verifier implements a focused FUURAA v1 rule, not general JSON Schema.

↗Internet Standard · December 2017IETF RFC 8259 · JSON

Defines the portable structured-data format parsed locally in the browser.

Boundary: Valid JSON cannot prove that a change occurred, evidence is authentic or a release decision is justified.

↗Published 26 January 2023NIST AI RMF 1.0

Connects governance, context, measurement and risk treatment across the AI lifecycle.

Boundary: Voluntary and use-case agnostic; it does not define a universal material-change threshold or approve a release.

↗Living resource · checked 16 August 2026NIST AIRC · AI RMF Playbook: Map

Connects system changes to affected context, people, impacts and accountable lifecycle roles.

Boundary: Suggested actions are informative and context dependent; the Playbook is being updated with the AI RMF.

↗Living resource · checked 16 August 2026NIST AIRC · AI RMF Playbook: Manage

Connects post-deployment monitoring, change management, renewed TEVV, risk response and decommissioning.

Boundary: It does not prescribe this record, sector duties or evidence sufficient for every agent.

↗Final published 26 July 2024NIST SP 800-218A

Adds AI-specific secure-development practices for model producers, system producers and acquirers.

Boundary: Secure-development guidance does not establish operating safety, change materiality or release approval.

↗Published 27 November 2023UK NCSC · Secure operation and maintenance

Calls for behaviour and input monitoring, secure-by-design updates and operational learning.

Boundary: High-level security guidance does not set task-specific tests, legal duties or universal thresholds.

↗W3C Recommendation · 30 April 2013W3C PROV-DM

Models entities, activities, agents, time, derivation and responsibility for provenance.

Boundary: Provenance can show lineage; it does not prove truth, control effectiveness or release suitability.

↗

Open the material change decision record →Read material change and recommissioning →Check an Agent operating-period record →Enter AI Evidence Atlas →Return to AI Knowledge Library →