Home / Trust
Scope. Authority. Proof.Refinery is designed to fail closed. Uncertain data is limited or blocked. A gateway read cannot execute a repair. No completed repair claim exists without an exact source readback and a durable receipt. These safeguards keep the limits visible before a decision is made.
The example consumer may read account status. An unrelated credit-limit field stays outside its scope.
A supported source change needs current policy, certification and exact authorization. AI confidence grants none.
enabledactiveThe source result must match, and the durable receipt must correlate with the authorized operation.
Your AI needs more than database access. It needs to know whether the data is usable for this task, right now.
Explains why data was released for a specific purpose and time, checked against approved freshness, quality, scope and policy requirements. A limited result carries explicit restrictions; a blocked result withholds the requested data.
A read check does not create a repair receipt.Proves an authorized source correction only after exact fresh readback and durable receipt evidence match the operation. A proposal, a routine check or an AI request is not proof of a repair.
The gateway only reads. Repair uses a separate governed path.Existing applications may keep direct database connections. Only consumers using the optional gateway receive its eligibility check; the source database remains authoritative. An AI can request a supported repair, but cannot authorize or execute one merely by asking.
The browser sample is available. Live customer connections, API/MCP access and repairs are not publicly released.
Freshness is currently table-level. Row-level freshness is not release-proven.
An approved AI use case receives only its allowed fields. A gateway request cannot call the repair executor — reading and writing are separate authorities, not separate permissions on the same one.
When the freshness signal is stale or unknown, or data is conflicted, disallowed, wrong-identity, or insufficiently proven, it is never quietly returned as trusted.
After an allowed repair, Refinery re-reads the authoritative source and keeps a durable receipt of the exact result. A successful write is not a verified outcome.
Every tier follows the same rules. Scope, authority and proof determine what Refinery may do.
| Boundary | What it means for your data |
|---|---|
| Approved reads | Only the fields and purpose you approve may pass. The gateway is read-only and cannot execute a repair. |
| Freshness | Table-level freshness is evaluated against the agreed window. Row-level freshness is not release-proven. A table signal cannot establish the age or correctness of every record. |
| Source changes | Supported repairs require current policy, exact authorization, connector and repair certification, an exact expected-before check, fresh source readback and durable receipts. |
| Uncertain data | Unknown values, identity conflicts and ambiguous financial facts are blocked or escalated. A model cannot invent the missing evidence. |
| Access today | The sample demo is available. Product access and purchasing are not open yet. Join early access to register interest. |
No customer-data engagement begins on trust alone. Purpose, scope, access, decision policy, and evidence plan are reviewed and documented first.
The exact AI or workflow decision, the PostgreSQL scope, the data class and volume, and the accountable business owner.
The minimum credentials, permissions, network path, storage, and retention needed for the agreed mode — and nothing beyond it.
Whether the path is read-only, setup-ready, certification-required, or proven for bounded repair. These are not interchangeable.
Which cases may be decided deterministically, which need a named human, and which are refused outright.
What will be recorded, how receipts are retained, and how the engagement is reconciled and audited afterwards.
The fit check and the waitlist need no credentials, no exports, and no production records. If someone asks you for those before the release gate, it is not us.
The demo runs the same refusals described on this page — including the one case that is deliberately never repairable.