Source example
DEMO · NEXUS STATE TRANSITIONcomputed on previewCANONICAL JCS / preview
Evidence BridgeEvidence Bridge maps your existing JSON or OpenTelemetry execution data into NexArt Certified Execution Records without requiring you to redesign your application payloads.
Use deterministic mapping to select the evidence that matters, review exactly what will be certified, create a cryptographically protected CER, verify it locally, and optionally submit it to the NexArt Node for independent attestation.
Evidence Bridge does not replace your logs, traces or monitoring. It converts selected execution data into independently verifiable evidence with deterministic transformation provenance and cryptographic integrity.
It can prove that the certified record has not been altered. It does not prove that the original source claims were true, complete or correct.
Open the Evidence Bridge from your NexArt dashboard to establish a secure session.
NexArt Evidence Bridge applies a published deterministic mapping profile to your application's existing JSON, creates and locally verifies structured NexArt execution evidence, and can optionally submit the unchanged evidence for separate NexArt Node attestation.
Trust boundary Bridge verifies the integrity of the transformation and preserves mapping provenance. It does not independently prove the truth or completeness of the source event.
Published revisions are immutable. Changes create a new revision linked to its exact profile hash.
The source preset controls only deterministic Auto-map aliases. It does not change the evidence type or runtime endpoint.
Choose the kind of execution evidence you want to create. Auto-map uses this target to suggest how fields in your existing JSON correspond to NexArt evidence semantics.
computed on previewCANONICAL JCS / previewMapping and evidence outcomes remain separate. No single badge represents the entire trust state.
Trust boundary Bridge verifies the integrity of the transformation and preserves mapping provenance. It does not independently prove the truth or completeness of the source event.
Protected values are hidden here after confidential evidence is created. Their mappings remain visible in Origin Trace, while the CER contains cryptographic commitments for those fields.
Public representation derived from BridgeMappedEvent—
Origin Trace shows where each evidence field came from in the source JSON. Protected values may not appear in the public mapped representation after confidential sealing.
Each signal answers a separate question. No single status represents the complete trust state.
————
Compact by design. Select a result to inspect source integrity, mapping, and evidence.
The mapping profile performs the deterministic transformation at the current host. No manual CER creation is required.
/api/v1/ingest/—/—Send the same native JSON your system already produces. Responses include independent mapping, eligibility, and verification fields.