Skip to content
Concept illustration of seven SBBX design principles arranged along a mountain path.
SBBX · SOVEREIGN BLACK BOX

An evidence protocol designed so that verification does not require trusting the producer.

SBBX is open-core and local-first. It is under active development, and each capability below is bound to a declared project state rather than a release claim.

PRIVATE ARCHITECTURE PREVIEW · M1 IN PROGRESS
PROPERTIES

Design properties

Seven properties define the protocol boundary.

These seven properties explain the SBBX design. Implementation, verification and release status are assessed separately; an illustration is not evidence that a capability is complete.

BOUNDARY

What SBBX can establish / What SBBX cannot establish

The left column applies only when corresponding evidence exists.

Can establish

Only when corresponding evidence exists.

  • Whether evaluated bytes match expected bytes.
  • Whether an integrity chain verifies.
  • Whether a supported signature verifies for the stated key role.
  • The verifier result for the supplied bundle.

Cannot establish

These remain outside what cryptography can support.

  • That captured source statements are factually true.
  • That an AI interpretation is correct.
  • That hallucinations are impossible.
  • Why a byte changed.
  • Actor intention.
  • Events that occurred outside the captured evidence boundary.
LAYERS

Architecture layers

L1

Capture boundary

Declared scope, consent binding and canonical serialisation.

  • Consent binding
  • Declared work boundary
  • Canonical serialisation
L2

Integrity layer

Append-only hash linking of canonical records.

  • SHA-256 record digests
  • Append-only linking
  • Tamper-evidence
L3

Role separation

Capture, approval and consent are distinct, attributed roles.

  • Capture role
  • Approval role
  • Consent role
L4

Local-first runtime

Operation without dependency on a remote service.

  • Local execution
  • No mandatory network path
  • Operator-held data
L5

Portable proof bundle

A self-contained export intended for independent checking.

  • Records + links
  • Declared key roles
  • Verifier inputs
L6

Offline verifier

Deterministic evaluation of the supplied bundle only.

  • Byte comparison
  • Chain evaluation
  • Signature evaluation
STATE

Capability states

A capability may be claimed only when its claim state is active.

CapabilityStateClaimNote
Canonical record modelCANDIDATENOT ACTIVESpecification under review inside the M1 scope.
Append-only integrity chainCANDIDATENOT ACTIVEDesign and reference logic in progress; not ratified.
Offline independent verifierPLANNEDNOT ACTIVEPlanned for the M1 acceptance set.
Portable proof bundle formatPLANNEDNOT ACTIVEFormat drafted; no released artifact is claimed.
Android durable encrypted-at-rest vaultDEFINEDNOT ACTIVEDefined intent only. Claim is not active.
SYGNET policy control planeDEFINEDNOT ACTIVEPost-M1 architecture preview. Not in the current product.