proof

Reference workflow and artifacts
Not claims. Outputs.
Reproducible on independent machines.
Reference workflow

This workflow is intentionally concrete:

capture →
inference trace →
commitment →
packaging →
offline verify →
deterministic replay →

Capture
Sensor streams are captured and deterministically segmented into fixed windows (“Segments”).

Inference trace
When analytics are used, inference artifacts include model identity and execution context identity and are bound to the exact input Segments consumed. A verifier traces outputs back to segment digests and timestamps and flags context mismatches.

Commitment
For each Segment, a cryptographic digest is computed during capture and chained to the prior Segment. A signed Manifest records boundaries, digests, continuity links, time source metadata, and key identifiers.

Packaging
Segments, the signed Manifest, provenance objects, and verification material are assembled into a .loko package suitable for transfer and case attachment.

Offline verify
On an air-gapped machine, a verifier recomputes digests, validates chain continuity, validates Manifest signatures, detects missing content, and produces a pass/fail report with specific error reasons.

Deterministic replay
A replay client reconstructs review timelines deterministically from Manifest boundaries. Independent machines reproduce identical segment boundaries and discontinuity markers. Replay and export events are recorded in an integrity-protected audit and handling ledger.

.loko package

Portable structure that survives transfer and audit.

# .loko package example
<session_id>.loko/
  manifest/
    manifest.json            # signed boundaries, digests, continuity links, time source, key IDs
    manifest.sig
  segments/
    seg_00000.mkv            # fixed window media segment
    seg_00001.mkv
    ...
  provenance/
    capture_context.json     # device, config, time source declarations
    inference_context.json   # model + runtime identity when analytics are used
  verification/
    public_keys/             # verification material for signature validation
    verifier_report.json     # pass/fail + explicit reasons
  ledger/
    handling_ledger.json     # replay/export/policy outcomes, integrity protected
Verifier Report

This is what independently verifiable looks like.

{
  "package_id": "…",
  "verified_at": "…",
  "verifier_identity": "…",
  "result": "PASS",
  "checks": {
    "manifest_signature": "PASS",
    "segment_digests": "PASS",
    "chain_continuity": "PASS",
    "missing_content": "PASS",
    "time_source": "DECLARED",
    "key_policy": "OK"
  },
  "replay": {
    "boundary_hash": "…",
    "discontinuities": []
  },
  "errors": []
}
Downgrade states

When systems cannot meet the highest bar, usability remains but the trust level must be explicit and governable.

EVIDENCE: passes offline verification and replay determinism

USABLE, NOT EVIDENCE: incomplete record or unverifiable components

ANALYTICS ONLY: inference present without committed integrity predicate
Procedural Legitimacy

On-record participation across standards, regulators and evidentiary rulemaking.

Receipts and acknowledgements are maintained.

download control plane pdf
NIST / NCCoE
Cyber AI Profile Workshop participation
Confirmed
Jan 14, 2026

U.S. SEC
Public comment filed (File 4-698)
Submitted and acknowledged
Jan 1, 2026

NIST
Public comments filed (multiple)
Filed and acknowledged
Dec 2025

U.S. Federal Courts
Evidence Rules submissions (FRE 707) including written testimony and hearing witness slot
Filed and acknowledged
Dec 2025 to Jan 2026

International & State-level record: Notices submitted to multiple state court bodies (including FL, NY, CA, IL, TX) and EU AI Act.
Dec 2025 to Jan 2026