Skip to content

0REI Immutable Evidence Systems

Evidence that carries its own proof.

Scroll

A record is sealed the moment it is written.

0REI signs every write with Ed25519, hashes it with SHA-256 and fixes its bytes with RFC 8785. The seal travels with the record, so anyone can check it later without the network, the database or us.

Follow one sealed packet down through the system: sealed, moved, found and verified.

Follow the packet

Seal it

Evidence Rail

Your application hands 0REI a record and gets back a sealed evidence packet. The record is put into one canonical byte form, hashed and signed with a key you hold, so any later change to it shows.

  • Canonical JSON (RFC 8785): the same record always produces the same bytes.
  • SHA-256 content hash bound to an Ed25519 signature.
  • You generate and keep the signing keys. Nothing is held in escrow.
SampleSealed record
Packet
PKT-SAMPLE-2048
Record
invoice.approved · INV-SAMPLE-2048
SHA-256
536a15eaa6ec…b9b8c1
Signature
ed25519 · sample key
State
Sealed
See how sealing works

Move it

TremorFrost Bridge

TremorFrost carries the packet between machines and agents as signed messages. Each sender signs with its own key, delivery is retried until it is acknowledged, and an agent wakes when a message is addressed to it.

  • Every message carries an Ed25519 signature from the agent that sent it.
  • At-least-once delivery from a single-writer message log.
  • Files travel too, with their SHA-256 sent in a signed message beside them.
SampleSigned transfer
Packet
PKT-SAMPLE-2048
From
system-a · sample agent
To
system-b · sample agent
SHA-256
536a15eaa6ec…b9b8c1
Signature
Verified on receipt
Read the security model

Verify it

Offline Verification

Anyone holding the packet can check it with the network unplugged. The verifier recomputes the hash and checks the signature on that machine alone, so an untouched copy reads valid and an altered one reads invalid.

  • Verification is a pure function: the same inputs always give the same answer.
  • No call home, no account and no vendor server are needed to check a seal.
  • An altered copy fails at the signature check and says so.
SampleAuthentic copy
Packet
PKT-SAMPLE-2048
amount_usd
18400.00
SHA-256
536a15eaa6ec…b9b8c1
Result
VALID
SampleTampered copy
Packet
PKT-SAMPLE-2048
amount_usd
81400.00
SHA-256
04b176fc61fb…9ec255
Result
INVALID at signature
Read the security model

Seal it · Move it · Find it · Verify it

The consoles

Each step has its own desktop console. Here is one sample packet going through all four.

  • Seal it: create a sealed packet from a record.
  • Move it and Find it: send the packet over TremorFrost and search for it in Zero Search.
  • Verify it: check the packet offline and read VALID or INVALID.
SampleOne packet, four consoles
Seal it
Sealed
Move it
Delivered, signature verified
Find it
Found with proof attached
Verify it
VALID
See the product

Hold the code to the same standardIn development

T3 Governance

We are building the same discipline into how our own software changes. A proposed change is attacked, checked and sealed before it lands, so the history of the code is evidence too.

  • A maker proposes the change.
  • A saboteur tries to break it and a verifier checks the result.
  • A sealer records the outcome so the trail can be checked later.
SampleChange record
Proposal
sample change
Maker
Proposed
Saboteur
Attacks run
Verifier
Checks passed
Sealer
Sealed
Ask about governance

Start here

Start a Proof Sprint

A Proof Sprint runs for two weeks at a fixed scope and a fixed price of $9,500. We deploy 0REI on your infrastructure and seal your real events, and your team verifies the seals offline.

  • 0REI deployed on your infrastructure with one ingestion path connected.
  • 100 or more sample seals, with five picked at random and verified offline.
  • The full fee is credited toward an annual license.
SampleSprint acceptance
Health check
Returns 200 OK
Seals
100+ generated
Offline check
5 random seals verified
Closeout
Report delivered
Start a Proof Sprint · $9,500