Trust in OCTOPUS is a property of the substrate, not a promise about the output. Here is each part of the trust model, what it means in practice, and what to ask to see.
Grounded, not guessed.
Last updated · Machine-readable: llms.txt · capabilities.json
Most AI platforms ask you to trust the output. OCTOPUS lets you verify it.
| Property | What it means | Ask to see |
|---|---|---|
| Evidence-backed | Every output is tied to the sources and reasoning that produced it. | One output traced back to its sources and its reasoning. |
| Coherence-gated | Consequential actions pass a coherence check before they execute. | An action the check stopped, and why. |
| Schema-validated | Data is validated against explicit schema contracts before it lands, so drift is caught before it spreads. | A record that failed validation, and what happened to it. |
| Fully audited | A complete, queryable, tamper-evident record of what happened, when, by whom and why. | One decision read back from the audit record: who, when, what and why. |
| Provenance throughout | The platform knows how knowledge entered, who created it and what it supports. | The provenance of one fact. |
| Human approval where it matters | Bounded autonomy where it is safe; on consequential moves, a person accepts at the point of effect: reversible moves with a short undo window, irreversible ones with a deliberate confirmation. | The lanes with autonomy turned up, and the moves that still wait for a person. |
| Tenant-isolated by design | Each tenant's knowledge is structurally separated, by architecture, not by policy. A tenant's credentials cannot reach another tenant's estate. | How isolation is enforced, and what a credential from one tenant can address. |
| Grounding guards | Two rules enforced as engineering practice, not prompt manners. Look up before you make up: ground in validated knowledge before generating. Verify the effect: confirm an action landed before reporting success. | A task whose report of success was checked against the effect. |
Three rules that keep the platform from telling you what you want to hear.
A signal the platform cannot read reports unknown rather than healthy. A held lane reads held, and a lane that went quiet is told apart from it.
A task closes on evidence that the effect landed. The agent's own report does not close it.
Anything that leaves the organization, such as an outbound message or a payment, needs a deliberate confirmation before it fires. A person accepts at the point of effect.
Inside your own tenant boundary, reached only through authenticated, tenant-scoped connections.
Each tenant's knowledge is separated by architecture, not by policy, and connections are authenticated and scoped to your tenant. Deployment options and regions are not published on this site; ask the team under early access.
The public endpoint at https://octo.ad/mcp has one tool, ask_octopus, and answers questions about OCTOPUS from public material. It exposes no customer data and no internal graph.
External-model counsel is redaction-checked and IP-gated. The content pre-publish gate blocks anything drawing on embargoed or pre-filing material until the protection window clears.
This site does not publish deployment options and regions; model-provider choice per tenant; the full connector list and the authenticated tool surface; single sign-on and role details; retention settings; pricing, customers, certifications and benchmarks. Ask the team.
We're onboarding a small group of teams that need agents they can depend on. Leave your work email. We'll remember it.
No spam. Your data is never sold. We only write about access.
Ask the octopusGrounded answers about OCTOPUS