It can check
- JSON, v1 rule identity and the fourteen-field structure
- Decision expiry, next-review date and obvious temporal conflicts
- Whether authority, monitoring, action evidence, change, incident and rollback fields are missing
FUURAA AI Knowledge Library · Browser-local verification tool
AI Agent Operating-Period Record Verifier
Check a FUURAA AI Agent operating-period record JSON locally in your browser for deployment identity, decision expiry, authority boundary, monitoring design, action evidence, incident response and review continuity. The file is not uploaded to FUURAA.
Verification workspace
Load an operating-period record, then close ten structural 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, deployment and decision, expiry, authority and cohort, monitoring design, action evidence, change, incidents, containment, rollback, residual unknowns and review continuity.
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 operating observations are true.
It cannot prove
- That observations occurred, logs are untampered or owner identities valid
- That signals are sufficient, thresholds correct, incident classification sound or recovery verified
- That a system is safe, fit to continue operating or legally, audit or certification compliant
FUURAA analysisOperating-period verification should first reject records that cannot bind version, authority, cohort, thresholds, window, action traces, human intervention, incidents, rollback, expiry and ownership. Even when all ten checks close, an independent reviewer must still open raw logs, repeat consequential measurements, verify incident handling and revoke the old decision after material change to the system, authority, environment, use or risk.
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 FormatDefines the JSON grammar and interoperable representation parsed in the browser.
Boundary: Valid syntax cannot prove that observations occurred, logs are authentic or continued operation is justified.
↗W3C Recommendation · 30 April 2013W3C PROV-DM · The PROV Data ModelFrames provenance through entities, activities, agents, derivations and responsibility.
Boundary: The FUURAA operating-period record borrows provenance concepts but is not a normative PROV serialisation.
↗Published 26 January 2023NIST AI RMF 1.0Connects 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 an operation.
↗Published 26 July 2024 · page updated 8 April 2026NIST AI 600-1 · Generative AI ProfileAdds generative-AI actions for monitoring, incident disclosure, provenance and third-party risk.
Boundary: Its actions still require prioritisation for the actual system, context and affected people.
↗Final · 3 April 2025NIST SP 800-61 Rev. 3Frames preparation, detection, response and recovery as integrated cybersecurity risk management.
Boundary: It addresses cybersecurity incidents broadly; this verifier adapts but does not equate those practices to Agent evidence.
↗