Proof bundle

A proof bundle is the set of artifacts we expect a deployment to be able to produce and retain. It is designed for audit, incident response, and change control in offline environments.

Architecture overview

High-level flow from inputs to outputs, with receipts as the durable evidence layer.

Threat model summary

Offline shifts the risk

Removing network dependency reduces exposure, but the device becomes the perimeter. Integrity, hardening, and update distribution matter more.

Primary attack surfaces

Common surfaces in air-gapped deployments:

Model/adapters supply chain and tampering
Insider risk and local privilege abuse
Artifact deletion or modification
Removable media handling and transfer procedure

Why this evidence model exists:

“Our CTOs are investing in sandboxes, but tools still have to be usable by teams.” — Business development leader, prime contractor
“We already have an AI policy. Some uses are allowed and others are restricted.” — Quality analyst, enterprise technology company

Full discussion: Offline Threat Model.

Compliance matrix

Framework	Status	Design intent	Evidence artifacts
CMMC	Target	Offline operation and traceability aligned to audit-driven procurement.	Receipts, manifests, hash-chained logs
AS9100	Target	Configuration control and reproducibility expectations for quality systems.	Version pinning, signed configs, proof bundles
ITAR	Constraint	Architecture shaped by controlled-facility data boundaries and restricted access.	Offline runtime, local-only processing, controlled update path

Release notes

Dated notes that indicate ongoing progress. These are site-facing milestones, not certification claims.

2026-02-06: Added receipt-backed cache credit accounting note (research).
2026-02-03: Equipment profiles bound into receipts as evidence (research).
2026-01-29: Published company overview and compliance roadmap (research).
2025-10-03: Documented offline dependency gravity and air-gap checklist (research).