[Record_1] Attorney memo...
Private file search
Search files without uploading them.
The public demo uses OSS OpenEncoder in your browser to turn documents into a small field signal. Gravitas searches that signal, then your browser maps the answer back.
Inspect the Boundary
What leaves, what comes back, what is ledgered.
Redacted example for one browser search. Byte counts vary by corpus and question. We do not keep traditional web logs. Paid search is tracked only through a pseudonymous append-only ledger.
{ corpus_field: "A94F...", inquiry_field: "19BC...", package_id: "pkg_..." }
Example upload: 889-949 bytes for signed paid-search quote/submit control payloads in the current public telemetry.
{ answer_pointer: { source: "field_a", byte_start: 644, byte_end: 698 }, proof: "abfb..." }
Raw answer returned by Gravitas: false. Browser maps the pointer back locally.
{ account: "d26c...", result_id: "res_...", dimension_receipt: "...", debit_event_hash: "..." }
No email, name, avatar, source text, decoded answer report, traditional web log, or traditional profile field is required for the product ledger.
Live Redacted Telemetry
Last 10 real paid-search requests.
Derived from the pseudonymous append-only ledger. No account handle, OAuth subject, package id, source text, query text, or answer text is shown.
| UTC | Encoder | Dims | Bytes | Score | Credits | Replay | Pointer | Proof |
|---|---|---|---|---|---|---|---|---|
| Loading redacted request telemetry... | ||||||||
How It Works
Local files. Field envelope. Local recovery.
Prepares deterministic field envelopes from your local text. No app install is required for the public path.
Receives compatible fields and metadata, then returns a proof-backed pointer/result package.
The readable answer is recovered from the local records already on your side of the boundary.
Mental Model
Not a locked book. A local library card.
You send the protected book. If someone gets the box, they physically have the book and the fight becomes key security.
The request carries a compact field signal, like a shelf coordinate. Without your local corpus and local mapback ledger, it does not contain the readable source.
It compares compatible field envelopes and returns a receipt-backed pointer. Your browser performs the local recovery.
This is not general-purpose encryption and not a claim that metadata disappears. Field envelopes and request metadata are sensitive derived metadata; raw source text is not present in the tested request payloads.
Encoder Lanes
Use the lane that matches the deployment.
Public browser/reference lane for no-friction review and compatible field-envelope generation.
Signed commercial/local lane for private deployments, customer packages, and high-performance evidence bundles.
Customers can redact, tokenize, shard, normalize, encrypt at rest, or apply local controls before field generation.
Boundary
Honest privacy language.
Stays localsource text, local mapback ledgers, client secrets, decoded reports
May be sentfield envelopes, request metadata, account/payment metadata, receipts
Known leakageenvelope shape, tensor counts, timing, context labels, repeated-request correlation
Proof
Proof and benchmarks are available, but not the first thing you need.
Legal-MLEB and MS MARCO values are local receipt-backed evidence claims, not official leaderboard acceptance. Retrieval quality and proof-surface metrics remain separated in the public report.
Buyer Briefs
Short pages for serious review.
Partnerships
Revenue partners for Defense, Legal, and Medical lanes.
Cash compensation is contingency-based and tied to realized revenue from sourced and closed enterprise deals. Email sram@mushku.com with redacted proof of closed enterprise deals. Do not send classified, privileged, regulated, customer-confidential, or non-public buyer material.