04 / Reisuka with Zero Search
Zero Search
A Reisuka family engine.
0REI seals it. Zero Search finds it.
Measured, 2026-09-28
- load
- 1,000 generated test records were sealed through the live API and closed into three anchored batches.
- offline
- One bundle from each batch verified VALID offline.
- tamper
- A copy with one flipped signature byte came back INVALID.
Test data, labelled generated=true, not customer data.
How it works
- Search. Ask in plain English and get ranked hits. Every sealed-record hit carries a proof handle.
- Prove. Get the record's offline proof bundle: the seal, its Merkle inclusion path, the anchored batch and the RFC 3161 timestamp token.
- Verify offline. Give the bundle to someone without your database or a network, and they get VALID or INVALID.
- Watch. A standing query fires once per matching record.
Nothing leaves the box
The service listens on 127.0.0.1 only. The embedding model runs locally from weights on disk. No query, record or vector is sent anywhere.
Secrets stay out of the index
Document text passes a redactor before it's indexed. Credential values are removed and their names kept.
Also in the family
The Agent Memory MCP gives AI agents memory they can prove: remember seals, recall searches, and prove returns the receipt.