S\P

SOVEREIGN\PROVENANCE · Product

Lab Provenance & Compliance

Record every dataset, training run, and synthetic output with compliance bundles ready on demand.

Start onboardingSee workflowStart checkoutDeveloper guide
Lab Provenance & Compliance

Protocol surface

Lab Provenance & Compliance

Live-ready

01

Identity

02

Seal

03

Ledger

Hash anchored
verified
Attestation signed
verified
Rights evaluated
verified

Protocol surface — not a live dashboard.

Who this is for

AI labs and safety teams documenting datasets, runs, and Accord obligations.

01

identity

Sovereign identities with attestations, keys, and trust graph bindings.

02

passport

Tamper-evident certificates binding identity, seal fragments, rights, and metadata.

03

accord

Machine-readable rights, cultural protocols, and consent operating as programmable policy.

04

runtime

Sovereign Runtime loop engine that automates registration, monitoring, and enforcement.

05

ledger

Append-only global ledger sharded by jurisdiction and mirrored into Guardian Nodes.

06

auditor

Independent auditor services and report pipelines for compliance and defense packages.

07

synthetic

Registration and attestation for AI-generated outputs and datasets.

What this gives you

  • 01Create lab identities, teams, and runtime channels tied to regulated obligations.
  • 02Register datasets, training runs, and models with lineage back to custodial datasets.
  • 03Capture synthetic outputs and Accord fulfillment to defend generative workloads.
  • 04Generate auditor-grade bundles for regulators, customers, or export controls.
  • 05Choose Sovereign Zones per dataset/model so EU, US, and APAC runs meet residency requirements.

Implementation path

  1. 01

    Connect lab identity + pipelines

    Provision an AI lab identity, register teams, and sync CI/CD or training pipelines that will emit Sovereign Runtime events.

    Use POST /api/v1/identity with persona=ai_lab and attach compliance contacts.

  2. 02

    Register training datasets & synthetic outputs

    Every dataset and generated corpus gets a Passport entry tied to Accord rules, dataset provenance, and intended use policies.

    Automate via SDK: dataset.register + synthetic.register for each training batch.

  3. 03

    Generate auditor-grade run reports

    Trigger runtime automations to capture lineage, weights, prompts, and Accord fulfillment—producing a downloadable compliance package.

    POST /api/v1/ai/runs + /api/v1/auditor/reports (available via jobs route).

Entitlements snapshot

  • ·5,000 artifact slots
  • ·2,000 dataset slots
  • ·500,000 API calls per month budget
  • ·Support level: enterprise
  • ·Runtime integrity scoring enabled
  • ·Auditor workflows + report export
  • ·Synthetic output attestation

Pricing & positioning

Pricing model: enterprise

  • ·Contracted per lab with dataset + run volume commitments.
  • ·Includes dedicated runtime channels and Auditor concierge.
  • ·Supports regulator and export-control ready report packs.

For developers

API focus

  • POST /api/v1/identity
  • POST /api/v1/datasets/register
  • GET /api/v1/datasets/:id/passport
  • POST /api/v1/models/register
  • POST /api/v1/models/:id/train
  • POST /api/v1/models/:id/infer
  • GET /api/v1/models/:id/passport

Integration routes

  • Lab Provenance cookbook

    Map datasets, runs, and model releases to SOVEREIGN\PROVENANCE objects.

    Open guide →

  • Synthetic registration example

    Register model outputs and integrity scoring callbacks.

    Open guide →

  • Auditor automation

    Export reports that regulators or customers can verify.

    Open guide →

Governed by The Covenant of Restraint, aligned with our Mission & Vision, and grounded in the Genesis Moment.