Home / Trust
Trust
We design around provenance, access boundaries, explicit authority and records that support review — and when we get something wrong, we correct it and say so.
We design around evidence, data boundaries, human authority and explicit refusals.
Every sentence on this site is bound to a named source in our claims register, and the site cannot be published until each one is approved. In our research stack an answer carries its sources, their dates and what the search did not cover.
Patra's document core performs no network I/O, proven by tests that block sockets and deny the network at the operating-system level. Karta runs commands in a sandbox with the network off by default. Where a system cannot yet keep data inside your environment, we say so.
People set what a system may do. Karta stops at protected paths until a person approves, and each approval is bound to the action it approves; in ChangeProof an approval counts only for the exact plan the reviewer was shown.
The research API declares which components ran and refuses an unapproved downgrade. When evidence is insufficient, it abstains and shows what it searched.
—
Our products are in development at different stages. We hold technical conversations and scoped assessments, and evaluate systems internally; engagements begin with the work, evidence and boundaries agreed together.
If something on this site matters to a decision, ask for its source. We will show you the record it rests on, or tell you plainly that it is not established yet.
