nexart.iodocs

    Evidence Bridge

    Evidence Bridge maps an existing JSON execution payload into a NexArt evidence family through a reviewed deterministic profile, then seals, verifies and submits the record for attestation.

    Evidence Bridge lets existing systems produce NexArt evidence without requiring them to adopt a NexArt-native payload format.

    Most applications, agents, workflow systems and automation platforms already emit execution data. The challenge is that every system structures that data differently.

    Evidence Bridge sits between the source system and NexArt's evidence formats. It receives an existing JSON execution payload, applies a reviewed deterministic mapping profile, checks whether the mapped event contains enough semantics for a supported NexArt evidence family, creates the appropriate confidential Certified Execution Record, verifies it locally, and submits the exact record to the NexArt Attestation Node.

    Architecture

    Evidence Bridge pipeline
    Source system
      |
Existing JSON payload
      |
Evidence Bridge
      |
Deterministic mapping profile
      |
Evidence eligibility
      |
+------------------------------+
| AI Execution V2              |
| Operational Execution V1     |
+------------------------------+
      |
Confidential CER
      |
Local cryptographic verification
      |
NexArt Attestation Node
      |
Signed Node receipt
      |
Independent RFC 3161 timestamp

    Evidence Bridge adapts evidence. It does not decide whether an action was good, compliant, authorized, or correct. The source system remains responsible for producing the execution facts it reports.

    Why Evidence Bridge exists

    Without Evidence Bridge, every system integrating with NexArt would need to construct NexArt evidence records directly. That works well for systems designed around the NexArt SDKs, but many existing platforms already have their own execution formats.

    For example, one system might report:

    {
  "execution_id": "exec_123",
  "action_type": "NODE_ISOLATION",
  "outcome": "APPLIED"
}

    while another might report:

    {
  "runId": "run_456",
  "operation": "isolate_node",
  "status": "success"
}

    The source semantics may be similar even though the JSON structures are completely different. Evidence Bridge solves the adaptation problem by keeping the mapping layer separate from the evidence layer:

    Source schema
    |
Mapping
    |
Normalized execution semantics
    |
Evidence target

    This separation means NexArt does not need a new cryptographic protocol for every source platform.

    Map once. Execute deterministically.

    Mapping profiles are created and reviewed before production use. AI may eventually assist with suggesting mappings during onboarding, but AI is not part of the production mapping path. Once a mapping profile is published, transformations are deterministic.

    Production rule
    same source payload
+ same mapping profile revision
+ same mapping engine version
= same mapped result

    Mapping execution:

    • does not call an LLM
    • does not execute arbitrary JavaScript
    • does not perform network lookups
    • does not allow user-supplied executable functions

    This keeps the transformation reproducible and auditable.

    Supported evidence targets

    AI Execution V2. Record family cer.ai.execution.v2, protocol 1.3.1, SDK @nexart/ai-execution. Use when the source represents an actual AI or model execution. See AI Execution through Evidence Bridge.

    Operational Execution. Canonical record family cer.consequential.execution.v1, protocol 1.3.1, SDK @nexart/consequential-execution. Use when the source represents a consequential system action or state-changing execution: infrastructure remediation, deployment, workflow state changes, financial operation execution, agent tool actions that actually execute, automation actions, resource isolation, configuration changes. See Operational Execution.

    A tool call, authorization decision, proposal, or model recommendation is not automatically a consequential execution. The source must contain sufficient evidence that an execution was attempted and report its outcome.

    System ownership

    Three services, three responsibilities
                        nexart.io
              Control Plane / Dashboard
              -------------------------
              Identity
              Plans
              API keys
              Entitlements
                    |
            short-lived handoff
                    |
                    v
              bridge.nexart.io
               Evidence Bridge
              -----------------
              Mapping profiles
              Source hashing
              Deterministic mapping
              Target eligibility
              Confidential CER creation
              Local verification
                    |
              exact sealed CER
                    |
                    v
               node.nexart.io
             Attestation Node
              -----------------
              CER verification
              Ed25519 receipt
              RFC 3161 timestamp
              Public resolution
    Machine clients
    Source application
      |
      | nx_live_ API key
      v
Evidence Bridge
      |
      | exact customer-attributed CER
      v
NexArt Node

    Where to go next