Product · Evidence Bridge
Keep your JSON. Add verifiable execution evidence.
Evidence Bridge takes the JSON your systems already emit and maps it, through a mapping profile you review and publish, into NexArt execution evidence. The record is verified locally at ingestion and can then be attested by a NexArt Canonical Node without being rebuilt.
- Explicit mapping profiles, reviewed by a human before use
- Deterministic: the same payload maps the same way every time
- Sealed once at ingestion, attested unchanged
Evidence Bridge uses your existing NexArt account and API keys. No separate login.
{
"source": "loan-review-service",
"target": "cer.ai.execution.v2",
"fields": {
"executionId": "$.run.id",
"model": "$.model.name",
"input": "$.request.payload",
"output": "$.response.text"
},
"confidential": ["input", "output"],
"idempotencyKey": "$.run.id"
}Workflow
From existing JSON to attested evidence
Author and review a mapping profile
You describe which fields of your payload become which evidence fields, and which are confidential. Auto-map can propose a draft, but a human reviews and publishes it. Published revisions are immutable.
Ingest a payload
The Bridge applies the published revision, builds the execution record, and verifies it locally. Repeated ingestion with the same idempotency key resolves to the same record instead of creating a duplicate.
Attest, separately
Attestation is its own step. The exact persisted record is submitted to a NexArt Canonical Node, which signs it. Nothing is rebuilt or resealed, so the certificate identity is unchanged.
Determinism
Mapping is a reviewed rule, not a guess
Evidence is only useful if the transformation that produced it can be explained later. Evidence Bridge separates authoring from execution so that every record can be traced back to a specific published profile revision.
Authoring time
- Auto-map proposes candidate field mappings
- A person reviews, edits, and approves them
- Publishing creates an immutable revision
Production time
- Only the published revision is applied
- No inference, no heuristics, no drift
- Each record references the revision that produced it
Evidence targets
Two supported record families
Confidential AI Execution V2
For model and agent runs. Sensitive fields are represented by cryptographic commitments, so prompts and outputs do not need to be shared to certify the run.
Confidential executionConsequential Execution V1
For state-changing infrastructure and workflow operations: the actions your systems take, recorded as independently verifiable evidence rather than as editable log lines.
Certified Execution RecordsChoosing an approach
Evidence Bridge or the NexArt SDK
Use Evidence Bridge when
- Your systems already emit structured JSON for each run or action
- You want evidence without embedding record construction in application code
- Several services or teams should share one reviewed mapping
Use the SDK when
- You want records built in-process, at the moment of execution
- You need full control over how each field is captured and sealed
- You are certifying inside a single application you own
Trust boundaries
- Your application decides what to send and remains the source of truth.
- Evidence Bridge maps, seals, and verifies. It does not author your data.
- The Canonical Node signs what it receives. It does not modify the record.
- Verification is independent: a sealed record can be checked at verify.nexart.io without trusting NexArt.
Data handling
- Ingestion JSON is hashed, parsed, and mapped, not retained as a raw record.
- Fields marked confidential are represented by commitments, not plaintext.
- What a record proves is integrity and provenance, not correctness.
- Evidence does not by itself establish compliance, legal admissibility, or that an outcome was right.
Frequently asked questions
- What is NexArt Evidence Bridge?
- Evidence Bridge is a NexArt product that takes JSON your application already produces and maps it, through an explicit and reviewed mapping profile, into NexArt execution evidence. The resulting record is verified locally at ingestion and can then be submitted unchanged to a NexArt Canonical Node for independent attestation.
- Do I have to change my application to use it?
- You keep your existing JSON shape. Work is still required: you review and publish a mapping profile that states exactly which fields become which evidence fields, and you send that JSON to the Bridge. There is no automatic, zero-effort integration.
- Is Auto-map used in production?
- No. Auto-map is an authoring aid that proposes a draft mapping for a human to review. Production ingestion applies only the published, immutable revision of a mapping profile, so the same input maps the same way every time.
- What is the difference between ingestion and attestation?
- Ingestion maps the payload, creates the execution record, and verifies it locally. Attestation is a separate step in which the exact persisted record is submitted to a NexArt Canonical Node, which signs it. Ingestion never depends on the node being reachable.
- Does the record change when it is attested?
- No. The record is sealed once at ingestion. The bytes submitted for attestation are the bytes that were persisted, so the certificate identity stays the same.
- Which evidence targets are supported today?
- Confidential AI Execution V2, for model and agent runs, and Consequential Execution V1, for state-changing infrastructure and workflow operations.
- Does Evidence Bridge store my raw payloads?
- Raw ingestion JSON is hashed, parsed, and mapped. It is not kept as a raw customer record. Fields marked confidential in a mapping profile are represented by commitments rather than by their plaintext values.
- Does Evidence Bridge prove that my AI was correct?
- No. It provides integrity and provenance: what was recorded, that it has not been altered since it was sealed, and that it can be checked independently. It does not establish that a decision or model output was correct or lawful.
- How do I sign in?
- Evidence Bridge reuses your existing NexArt account and API keys. There is no separate Bridge login, plan, or billing system.
Start from the JSON you already have
Sign in with your existing NexArt account, publish a mapping profile, and ingest your first payload.
Related: How NexArt works · Certified Execution Records · Confidential Execution · Independent Verification · Product stack