nexart.iodocs

    What is NexArt

    NexArt turns AI and code executions into cryptographically verifiable evidence.

    The problem

    • Logs describe what happened but do not prove it.
    • Logs can be altered, incomplete, or reconstructed after the fact.
    • Audits rely on trusting systems, not verifying them.
    • There is no standard way to prove that an AI or code execution produced a specific output from a specific input.

    What NexArt does

    Every execution becomes a Certified Execution Record (CER). CERs capture:

    • Inputs
    • Outputs
    • Parameters
    • Metadata
    • Optional contextual evidence such as signals

    The record is hashed (SHA-256) to produce a certificateHash. Any change to the record breaks the hash.

    Single executions are identified by a certificateHash. Multi-step workflows are identified by a projectHash.

    Logs describe events. CERs prove execution integrity.

    Core components

    SDK

    Creates CERs and verifies them locally. See AI Execution SDK.

    CER (Certified Execution Record)

    The atomic unit of proof. One execution, one sealed record. See CERs.

    Project Bundles

    Group multi-step workflows into a single verifiable structure with a projectHash. See Project Bundles.

    Node

    Independent witness and public trust surface. Provides attestation and lookup. Verification always happens independently. No trust in NexArt is required to verify a record. See Attestation Node.

    verify.nexart.io

    Public verification interface. Runs verification locally in the browser. See verify.nexart.io.

    How it works

    1. Execute: AI or code runs via SDK
    2. Record: CER is created
    3. Seal: certificateHash is computed
    4. Attest (optional): node issues attestation
    5. Bundle (optional): Project Bundle created, projectHash derived
    6. Verify: using SDK or verify.nexart.io

    What you can prove

    • What ran
    • With what inputs
    • What it produced
    • In what sequence (for workflows)
    • That it has not been altered

    Where NexArt fits

    • AI agents
    • Multi-step workflows
    • Compliance and audit trails
    • Decision traceability
    • Evidence-backed automation

    What NexArt is NOT

    • Not observability
    • Not logging
    • Not model evaluation
    • Not correctness validation

    NexArt confirms the integrity of what was recorded and, when applicable trust material is present, that it was attested by the node. It does not establish that an AI output was correct, fair, lawful, or complete. The completeness and truthfulness of the recorded execution data depend on the integration and capture boundary.

    What NexArt guarantees

    • Integrity of what was recorded (tamper-evidence via hashing)
    • Independent verification without trusting NexArt infrastructure
    • Attestation as an optional layer (node receipt, not required for integrity)

    NexArt does NOT guarantee completeness. Recording every step is the developer's responsibility.

    Next steps