Fragmented story
Reasoning, action, and human review live in separate systems. Reconstructing one decision under examination is slow to impossible.
Decision provenance for consequential AI
Provenant turns every consequential decision from physical systems and multi-step agents into a signed, hash-chained Decision Record. Your model and data never leave your environment. Only sealed commitments cross the boundary.
Built for high-stakes AI · aerospace beachhead · horizontal core · agentic + physical
The problem
Whether an agent approved a transaction or a physical model cleared a vehicle, three failures show up under examination — and each is fatal to audit, liability, and certification.
Reasoning, action, and human review live in separate systems. Reconstructing one decision under examination is slow to impossible.
Conventional logs sit inside writable storage. Auditors increasingly discount records that cannot prove they have not been altered.
The critical question is the same across money and machines: what did the system decide, on what basis, and can you prove this is the original record?
Product
Provenant is a decision-provenance platform: capture at the edge, verify on the platform. Aerospace is the first vertical — not the product’s identity. The same core seals agent trajectories and physical control decisions.
Pin environment fingerprints, model identity, and enough context that a decision can be attested — not just logged.
A single Decision Record schema — input, reasoning, confidence, OOD flags, output — fed by physical or agentic adapters.
Per-source hash chain, Ed25519 signatures, Merkle transparency log, optional RFC 3161 timestamp anchors.
Rebuild any decision, answer why, export self-verifying evidence packages for DO-178C / EASA, EU AI Act Art. 12, and more.
How it works
Register tenant, content-addressed Model ID, and source public keys. Private keys stay at the edge.
Adapter seals input · reasoning · output hashes, chains prev_record, signs with Ed25519, buffers if offline.
Platform four-check pipeline: schema, signature, identity reconciliation, chain continuity — then ledger leaf + payloads.
Why narrative, residual trails, inclusion proofs, and regulator-ready evidence packages — months later, still intact.
from provenant import CaptureSession, Signer, FileChainStore
from provenant import JsonlEmitter, ThresholdCapture, compute_model_id
model_id = compute_model_id(
weights="checkpoints/aeromind_pinn.pt",
config={"arch": "tilt_rotor"},
quant="fp32-cpu",
)
session = CaptureSession(
tenant_id="op-northstar",
source_id="N-AM042",
model_id=model_id,
signer=Signer.load("keys/n-am042.key"),
chain=FileChainStore("provenance/chain"),
emitter=JsonlEmitter("provenance/buffer"),
policy=ThresholdCapture(), # FULL when flagged / OOD
)
sealed = session.capture(
input_payload=telemetry,
reasoning=health_result, # model rationale ("why")
output={"decision": "CONDITIONAL"},
output_label="CONDITIONAL — battery limiting",
confidence=0.88,
)
from provenant import CaptureSession, FullCapture, Signer
from provenant.integrations.agentic import AgenticCapture
session = CaptureSession(
tenant_id="t-…", source_id="agent-1", model_id="MID-agent",
signer=Signer.generate(), policy=FullCapture(),
)
cap = AgenticCapture(session, task={"instruction": "…"})
# Each step seals on the hash chain…
cap.step("plan", reasoning=plan, output=plan_out)
cap.step("tool_call", input_payload=tool_in, output=tool_out)
cap.step("llm", reasoning=thoughts, output=answer)
# Parent record binds the full trajectory
parent = cap.finalize()
# verify_trajectory(parent, steps) → ok
# Platform
GET /records/{decision_id}/why
# → narrative + sealed model_rationale + ledger proof
# Offline SDK
from provenant import build_decision_explanation
why = build_decision_explanation(
sealed.record,
payloads={"reasoning": reasoning, "input": inp, "output": out},
public_key_hex=signer.public_key_hex,
)
print(why["narrative"])
print(why["why"]["model_rationale"])
Modalities
It would be marketing fluff if agentic and physical were two products sharing a logo. They are not — the provenance primitives are identical. Only the capture adapter and compliance profile change.
Instrument health scorers, control loops, and supervisory models. Content-addressed model identity, environment fingerprints, residual / rule trails in reasoning, episode windows for flight-recorder style capture.
Multi-step agents seal each plan, tool call, retrieval, and LLM step. A parent record binds the trajectory. Same chain, same ledger, same Why path for auditors and risk teams.
Architecture
Provenant never ingests your model or raw training data. Capture is push-only. Payload and proof are deliberately split so the ledger stays lean and externally verifiable.
signed records →
hashes · metadata · optional FULL payloads
Only cryptographic commitments, manifests, and runtime fingerprints. Weights stay home.
The platform never reaches into your runtime. Attack surface stays where you control it.
Sensitive bytes in object store; hashes on the ledger. Reconstruct when authorized — not by default.
Aircraft and air-gapped agents produce correct, chained records offline; sync later with drain.
Why now
Regulation, agentic complexity, and emerging standards converged. Provenant is built toward the full stack auditors and certification bodies increasingly require — not another dashboard of editable logs.
EU AI Act · Art. 12
High-risk systems must keep logs that enable traceability of results with integrity — a horizontal mandate spanning physical and agentic systems.
EASA / aerospace
AI for aviation is expected to be explainable, predictable, and traceable. Decision trails must survive certification and investigation timelines.
Emerging standards
Industry drafts for cryptographically verifiable decision audit trails confirm the category — and that point solutions will not compose cleanly.
Platform
Dashboard, decisions, Why, evidence, and integrity events. Deep-link any decision from your OEM tools.
Content-addressed Model IDs. Identity changes are explicit registrations — never silent overwrites.
RFC 6962 roots, inclusion and consistency proofs, signed tree heads, dual file + RFC 3161 anchors.
FULL, HASH_ONLY, or THRESHOLD — store payload bytes only when reconstruction is worth the cost.
Self-verifying exports: narrative, payloads, attestation, and machine-readable proof for third parties.
Ingest, ledger, and anchor health for production SRE — not just a pretty status page.
Design partners
We partner with aerospace and agentic teams who need decisions to survive audit — not just demos. Beachhead: physical AI in aviation. Horizontal ambition: every vertical where “why” is a liability question.