End-to-End Walkthrough

What leaves, what stays, and how the answer returns.

This is the shortest honest explanation of the product boundary. Customer data and local recovery stay local. Gravitas receives a compatible field envelope and returns a receipt-backed pointer.

Example

One local corpus, one question, one local recovery.

LOCAL RECORDS
------------
[Record_1] County filing mentions a lease assignment and possible title gap
[Record_2] Pipeline outage notice affects a nearby production schedule
[Record_3] Court docket references a mineral ownership dispute

LOCAL QUESTION
--------------
Which current headline should I review first for commercial or operational risk?
1

Local Preparation

The customer uses OpenEncoder, Ionizer, or a compatible encoder inside their own environment. Local source records, local ledger, and client secret stay local.

2

Outbound Envelope

The request contains field tensors, stable field IDs, context/submission metadata, and account authorization. It should not contain raw source text or the local recovery ledger.

3

Field Resolution

Gravitas operates on the field envelope and returns a receipt-backed pointer. It does not need the readable source corpus to cross the service boundary.

4

Local Map-Back

The customer-side ledger maps the returned pointer back to readable text already held locally.

5

Replay

The saved result receipt can be replayed without re-debiting credits or mutating the original result record.

6

Audit

Reviewers inspect the request envelope, proof output, package receipt, and result receipt to verify the boundary.

Inspectable Request Boundary

Use DevTools or a local proxy to check the payload.

STAYS LOCAL                         MAY BE SENT
----------------------------------  ---------------------------------------------
source text                         corpus field tensor
query text before encoding          query field tensor
local recovery ledger               field IDs and context/submission metadata
client secret                       account authorization and package receipt
decoded answer report               quote, debit, result, and replay receipts

Plain Result

The user should see an answer, not an internal record id.

The public demo displays the locally recovered answer text first, then the receipt and pointer proof. The pointer exists for audit. The answer text exists for the human.

HUMAN VIEW
---------
Answer: Court docket references a mineral ownership dispute

RECEIPT VIEW
------------
Gravitas returned a receipt-backed pointer.
Browser answer selection authority: false
Raw answer returned by Gravitas: false
Local map-back recovered the readable answer from local records.