A domed capitol building under an overcast sky, its facade traced by a network of light

Government

NDAA FY2026 §1513 makes model provenance part of federal procurement. CID makes provenance a property of the build.

Book a Demo
Overview

Accountability and sovereignty, by architecture.

Every pipeline stage produces a tamper-evident attestation. Provenance isn't a document assembled after the fact — it is part of how the model is built.

0Perimeter Crossings

Agency data never leaves the accreditation boundary. Model updates are all that cross it.

§1513Procurement Provenance

NDAA FY2026 provenance evidence generated as a property of the build, not a document after it.

100%Pipeline Attestation

Every stage, data prep through deployment, produces a tamper-evident record.

Air-gapSovereign Deployment

Fully air-gappable on-prem deployment available today for sealed environments.

Architecture

Provenance isn’t assembled after the fact. It’s how the model was built.

  • A deploy stage cannot exist without a prior validate stage.
  • No flag, no override, no debug mode bypasses the gate.
  • Every stage produces a tamper-evident attestation.
  • Fully air-gappable — agency data never crosses the perimeter.
  • Raw data stays inside each boundary; only model updates move between them.
  • The complete pipeline runs inside the accreditation boundary.
  • Attested lineage from data prep through deployment.
  • Checkable by any authorized party.
  • Provenance is a property of how the model was built, not a document assembled after.
  • Actively pursuing authorization.
  • Sovereign on-prem deployment available today for air-gapped environments.
Where it applies

Where agencies put it to work.

Cross-agency threat detectionShared models across organizational boundaries — each agency's data stays inside its perimeter.
Disease surveillancePublic-health signal across jurisdictions without centralizing records.
Improper-payment detectionCross-program fraud patterns, recorded contributions, no pooled beneficiary data.
Sovereign node / air-gappedSealed
Perimeter crossings
0
Pipeline location
In boundary
Attestations
Tamper-evident
FedRAMP Moderate
In progress
Recommended deployment

The whole pipeline, inside the accreditation boundary.

On-prem · Sovereign. Fully air-gappable deployment for sovereignty requirements: training, attestation, and audit log all run inside the boundary, and nothing leaves but model updates.

Partner with us

Oversight gets evidence, not assertions.

Stop assembling accountability packages by hand. STEAV records every pipeline stage as it runs, giving oversight bodies what §1513 asks for without the reporting overhead.

Become a Partner

First pipeline run in 4–6 weeks. Sovereign on-prem available today for air-gapped environments.

Run a pilot
What a pilot includes

A dedicated environment inside your accreditation boundary

Your first cryptographically signed execution record

A §1513-ready provenance export for a real procurement

A named STEAV engineer through go-live

Programme
Drawn to scale · weeks from kickoff
12 WEEKS04812Week 0Weeks 4–6Weeks 8–12
Week 0

Scoping

We map one workflow and stand up an environment inside your boundary.

Weeks 4–6

First attested run

A signed execution record you can hand straight to oversight.

Weeks 8–12

Production deployment

Live pipelines producing §1513 provenance on every run.