S\P

SOVEREIGN\PROVENANCE · Product

Dataset Passport

Publish a tamper-evident passport for every dataset with trust metadata and Accord guardrails.

Start onboardingSee workflowStart checkoutDeveloper guide
Dataset Passport

Protocol surface

Dataset Passport

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

Museums, libraries, universities, and civic agencies acting as dataset stewards.

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

ledger

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

05

guardian

Regional enforcement nodes that watch feeds, sync ledger shards, and raise disputes.

06

runtime

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

What this gives you

  • 01Describe datasets, owners, storage locations, and refresh cadence in a canonical manifest.
  • 02Bind Accord policies that govern AI training, civic re-use, and downstream obligations.
  • 03Mirror passports into Guardian Nodes so labs and cities can verify instantly.
  • 04Expose shareable passport APIs so partners can confirm custody without manual workflows.

Implementation path

  1. 01

    Define the dataset & steward

    Create or link an institutional identity, describe the dataset contract, schema, refresh cadence, and custodians.

    POST /api/v1/identity for the steward; include governance metadata + contact handles.

  2. 02

    Register storage + Accord policy

    Point to storage (S3, GCS, IPFS, on-prem), capture checksums per shard, and express Accord policies for AI, civic, or commercial usage.

    Use POST /api/v1/passport with type=dataset and include accordRules + storage URIs.

  3. 03

    Publish the dataset passport & telemetry

    Anchor the passport to the ledger, mirror to Guardian Nodes, and expose a Passport share link or API for labs to verify.

    Call POST /api/v1/guardian/reports to broadcast, or embed the Explorer widget.

Entitlements snapshot

  • ·200 artifact slots
  • ·500 dataset slots
  • ·150,000 API calls per month budget
  • ·Support level: standard
  • ·Runtime integrity scoring enabled
  • ·Auditor workflows + report export
  • ·Guardian Node orchestration

Pricing & positioning

Pricing model: tiered

  • ·Priced by active dataset passports and storage connectors.
  • ·Guardian publication bundle unlocks civic + lab distribution.
  • ·Ideal for institutions that need predictable annual budgets.

For developers

API focus

  • POST /api/v1/identity
  • POST /api/v1/passport
  • POST /api/v1/guardian/reports
  • GET /api/v1/provenance/verify
  • GET /api/v1/guardian/reports

Integration routes

  • Dataset Passport guide

    Step-by-step for civic, research, and institutional dataset stewards.

    Open guide →

  • Storage binding recipe

    How to anchor S3/GCS buckets and IPFS roots with checksums.

    Open guide →

  • Guardian publishing API

    Broadcast dataset passports to cities & labs.

    Open guide →

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