01
Operator-directed, not platform-orchestrated.
Disquiet is the tool surface; your reasoning client is the reasoner. We don't run autonomous agents on your behalf. The operator stays the inner loop. Every decision goes through you.
Disquiet is the tool surface; your reasoning client is the reasoner. We don't run autonomous agents on your behalf. The operator stays the inner loop. Every decision goes through you.
The model cannot act directly. No shell, no eval, no raw code. Tool outputs return as structured facts on labeled axes, scoped to what the reasoner needs. Drift is bounded; context stays clean; token spend stays predictable. Engagements don't balloon the way transcript-stuffing agents do.
Tools surface orthogonal axes: the facts, the dimensions, the observed responses. They don't collapse into a "vulnerable: yes/no" conclusion. The reasoner sees the data; the reasoner draws the inference. You stay in charge of the call.
The toolset was demanded by the model under adversarial pressure during the build. Every capability earned its place against a real target before it was written.
Each operator gets a dedicated isolated microVM with its own data key, audit chain, and signing key. No multi-tenant tag-walls, no commingling. Operator-controlled egress when the runner is in use: source IP, network path, execution context yours.
Web apps, APIs, internal services, Active Directory — same primitive surface across 180+ operations across 23 domains, composable rather than pre-canned. Scope declared on intake; every tool call gated against scope before traffic egresses. Findings carry full evidence: request and response envelopes, reproduction, remediation, reasoner-scored severity.
The decisions that bound an engagement, and the actions taken under them, live in a hash-chained append-only log. Chain heads anchor every ten minutes to four independent substrates with four different trust models: Bitcoin (via OTS), FreeTSA + DigiCert (RFC 3161), and Sigstore Rekor (transparency log). The verifier is a binary that re-walks the chain, replays the Merkle proofs, and validates each receipt against its substrate offline. Disquiet is not in the attestation trust path; neither is any single anchor. If Disquiet disappears, your verification stays valid.