FUURAA AI Knowledge Library · Index check tool

AI Agent Lifecycle Evidence Index Check Tool

Run ten structural, reference-integrity and temporal checks on a lifecycle index JSON locally in your browser. The file is not uploaded to FUURAA.

Tool statusPublicly usable · no upload by defaultCheck rulefuuraa.ai-agent-lifecycle-evidence-index/v1Sources checked17 August 2026

Index check workspace

Load a lifecycle index, then close ten bounded checks.

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

AI Agent lifecycle evidence index 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 an index is reviewable; it neither opens references nor judges evidence or decisions reliable.

It can check

JSON, v1 rule identity and the fifteen-field structure
Whether six-stage references, current decision, active release, integrity context and handover fields are missing
Current-decision expiry and whether none/not-applicable states are explicit

It cannot prove

That references exist, are accessible, untampered, correctly hashed or authentic
That records are sufficient, unknowns closed, controls effective or the current decision covers the actual system
That the system is safe, operation justified or legal, compliance, audit and certification requirements met

FUURAA analysisMachine checking should first block indexes that cannot bind the exact system, six-stage lineage, current authority, active release, expiry, reference integrity, transfer limits and ownership handoff. Even when all ten checks pass, reviewers must independently open every authoritative record, verify stable identifiers and hashes, challenge stated absences, and confirm that the active system is covered by an unexpired decision.

Standards and method sources

Use primary specifications to design an inspectable index 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 tool implements a focused FUURAA v1 rule, not general JSON Schema.

↗Internet Standard · December 2017IETF RFC 8259 · JSON

Defines the portable data format parsed locally in the browser.

Boundary: Valid JSON cannot prove that referenced evidence exists, is authentic or supports a decision.

↗Published 26 January 2023NIST AI RMF 1.0

Provides lifecycle-wide outcomes for governing, mapping, measuring and managing AI risk.

Boundary: Voluntary and use-case agnostic; it does not authorise a system or prescribe this index.

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

Connects deployment, monitoring, incident response, change management and decommissioning actions.

Boundary: Suggested actions require adaptation and are not proof that an organisation performed them.

↗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 is not operating authorisation, safety evidence or an audit result.

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

Connects monitoring, secure updates and lessons learned to deployed operation.

Boundary: High-level security guidance does not define task-specific evidence or retention periods.

↗W3C Recommendation · 30 April 2013W3C PROV-DM

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

Boundary: Provenance shows lineage; it does not prove truth, authenticity or decision quality.

↗

Open the lifecycle evidence index →Read the lifecycle evidence chain →Enter AI Evidence Atlas →Return to AI Knowledge Library →