FUURAA AI Knowledge Library · Browser-local verification tool

AI Agent Incident Decision Record Verifier

Check a FUURAA AI Agent incident decision record JSON locally in your browser for incident identity, authority containment, evidence bundle, impact, causal challenge, recovery verification, independent review and decision expiry. The file is not uploaded to FUURAA.

Tool statusPublicly usable · browser-local processingVerification rulefuuraa.ai-agent-incident-decision-record/v1Sources checked5 August 2026

Verification workspace

Load an incident decision record, then close ten structural, evidence and temporal checks.

Choose a local JSON file, paste content, or load a blank template or clearly marked complete fictional example. Verification reads only the text in this page.

Checks cover schema identity, incident and deployment, clocks and trigger, containment, evidence custody, impact, competing causes, recovery, independent review and the expiring decision.

AI Agent incident 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 the incident, cause or re-authorisation is true.

It can check

JSON, v1 rule identity and the fifteen-field structure
Whether incident, authority, clocks, containment, evidence, impact, cause and recovery fields are missing
Decision expiry and obvious gaps in scope, exclusions, ownership and reopen conditions

It cannot prove

That an incident occurred, logs are untampered, custody complete or owner identities valid
That impact is complete, causality established, repairs effective or recovery tests sufficient
That a system is safe, re-authorisation justified or legal, forensic, audit or certification compliant

FUURAA analysisIncident-decision verification should first reject records that cannot bind incident, version, authority, clocks, trigger, evidence bundle, impact, counter-evidence, recovery tests, independent review, expiry and reopen conditions. Even when all ten checks close, a reviewer must still open raw evidence, challenge causality, repeat consequential tests and confirm that the new decision covers only the scope supported by evidence.

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: The document is an expired Informational Internet-Draft. This verifier implements a focused FUURAA v1 rule, not general JSON Schema.

↗Internet Standard · December 2017IETF RFC 8259 · JSON Data Interchange Format

Defines the JSON grammar and interoperable representation parsed in the browser.

Boundary: Valid syntax cannot prove that an incident occurred, evidence is authentic or re-authorisation is justified.

↗W3C Recommendation · 30 April 2013W3C PROV-DM · The PROV Data Model

Frames provenance through entities, activities, agents, derivations, time and responsibility.

Boundary: The FUURAA incident record borrows provenance concepts but is not a normative PROV serialisation or integrity proof.

↗Published 26 January 2023NIST AI RMF 1.0

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

Boundary: Voluntary and use-case agnostic; it does not prescribe this verifier or certify a decision.

↗Final · 3 April 2025NIST SP 800-61 Rev. 3

Frames preparation, detection, response and recovery as integrated cybersecurity risk management.

Boundary: Cybersecurity guidance broadly; this verifier does not replace an organisation's incident plan or forensic process.

↗Published 26 February 2024NIST Cybersecurity Framework 2.0

Provides high-level outcomes for governing, identifying, protecting, detecting, responding and recovering.

Boundary: It does not prescribe how outcomes must be achieved or validate a specific response decision.

↗

Open the incident decision record builder →Read incident response and re-authorisation →Verify an Agent operating-period record →Continue to the human review protocol →Enter AI Evidence Atlas →Return to AI Knowledge Library →