AI labs & ML teams

Lab Provenance & Compliance onboarding

Full-stack provenance, lineage, and auditor automation for AI labs that must document datasets, runs, and releases.

Connection

Requests hit the SOVEREIGN\PROVENANCE API directly. Bring your own API key and tenant to test in staging. Each step includes the canonical payload you can tweak.

0 of 4 complete

  1. 01 Register the AI lab identity
  2. 02 Register a training dataset
  3. 03 Record a training run with dataset bindings
  4. 04 Export an auditor-ready compliance bundle

Live ledger stats appear here once artifacts, nodes, or synthetic activity exist for this tenant. Connect a staging key to load them.

Step 01

Register the AI lab identity

Provision an identity for the lab, include compliance contacts, and store runtime callback URLs for auditor alerts.

Waiting

HTTP request

POST
Read docs →

Payload

Response

Response will appear here after you run this step.

Step 02

Register a training dataset

Describe dataset lineage, custodians, storage location, and associated Accord rules before any training begins.

Waiting

HTTP request

POST
Read docs →

Payload

Response

Response will appear here after you run this step.

Step 03

Record a training run with dataset bindings

Attach datasets, hyperparameters, and runtime metadata. Sovereign Runtime will emit lineage + integrity records.

Waiting

HTTP request

POST
Read docs →

Payload

Response

Response will appear here after you run this step.

Step 04

Export an auditor-ready compliance bundle

Generate the SOVEREIGN\PROVENANCE audit bundle for a regulator or enterprise partner. Default format is `generic`.

Waiting

HTTP request

GET
Read docs →

Response

Response will appear here after you run this step.