01 / YOUR JSON
Source example
DEMO · NEXUS STATE TRANSITIONRAW DIGEST
computed on previewCANONICAL JCS / previewEVIDENCE BRIDGE / OVERVIEW
Turn the JSON you already produce into NexArt-ready execution evidence.
Define how your existing JSON maps to evidence fields. Inspect eligibility and integrity signals before publishing.
CURRENT SCOPEYour JSON
→ EvidenceNo source format changes.
No fabricated CERs.
→ EvidenceNo source format changes.
No fabricated CERs.
THE FLOW
Not eligible is an informational outcome, not an error.Four clear, inspectable stages.
01Your JSONYour existing record
→02MappingExplicit rules
→03Evidence checkRequired semantics
→04NexArt evidenceCER when eligible
REGISTRY
Current mapping profiles
MAPPING PROFILES / CREATE
Define a truthful transformation.
Published revisions are immutable. Changes create a new revision linked to its exact profile hash.
01 Source02 Mapping03 Preview04 Publish
02 / MAPPING
Evidence fields
YOUR JSON PATH / VALUEINTERNAL FIELDTRANSFORMREQUIREMENT
Required fields are validated before publish.
MAPPING PROFILES / PREVIEW
Review the mapped output and evidence check.
Mapping and evidence outcomes remain separate. No single badge represents the entire trust state.
Run a preview from the mapping screen first.
MAPPED OUTPUT
Your data in the internal evidence shape
Technical type: BridgeMappedEvent—
ORIGIN TRACE
Where each field came from
—
EVIDENCE STATUS
Independent status signals
Technical details and hashes
————
RESULTS
Transformation results.
Compact by design. Select a result to inspect source integrity, mapping, and evidence.
RESULT ID / SOURCESTATUS
Results appear after a profile receives native JSON.
Select a result to inspect its evidence record.
INTEGRATION
Send the JSON you already produce.
The mapping profile performs the deterministic transformation at the current host. No manual CER creation is required.
POST
/api/v1/ingest/—/—Send the same native JSON your system already produces. Responses include independent mapping, eligibility, and verification fields.