SPE — Executive Technical Brief

V1.0 // Q1 2026

Portable digital integrity proofs, verifiable offline.

SPE is a technical system that produces self-contained integrity proofs for digital objects. It enables any party to verify whether a file is bitwise identical to the version that was sealed at a given time.

The system is intentionally built around three explicit constraints:

  • 01. No custody
  • 02. No authority
  • 03. No blind automation

SPE does not ask for trust. It enables verification.

Section 01 // The Structural Problem

Digital verification has entered a fragile phase: it is increasingly easy to modify content and increasingly common for “proof” to depend on the party who issued it.

Platform Dependence

Verification is often tied to the issuer. If the provider disappears, the proof becomes unverified. SPE produces proofs that remain verifiable independently of the provider.

Category Errors

Many systems mix integrity with truth or authorship. SPE avoids this: VALID does not mean “true”—it means “unchanged”.

AI Mutability

AI inputs and outputs are unstable. SPE enables integrity proofs for inputs before inference and outputs after inference, without storing content.

Section 02 // Protocol Operation

01

Seal

User creates a portable proof bundle (ZIP) containing cryptographic artefacts. User retains full custody.

02

Verify Bundle

The verifier validates that the proof bundle itself has not been altered before checking the target object.

03

Compare

User compares a candidate file against the sealed reference. Results are binary: MATCH or MISMATCH.

Verifiable offline
By different parties
Across different systems

Section 03 // Scope Boundaries

Non-Negotiable Boundaries

  • No truth or record accuracy claims
  • No authorship or provenance guarantees
  • No replacement for legal/human judgment
  • No content interpretation

Stateless Infrastructure • Deterministic Proof