8.0 Qaduceus AI
An intelligence that shows you its thinking.
A sovereign assistant with a workspace and artifacts, its reasoning visible as it runs — on device by default, or on QERYX-operated hardware; the attested-enclave lane arrives when the attestation is real. Every capability described is built, and no other is claimed.
Capabilities listed are the ones built, and no others.
- In development
- Built-only capability list
- No third-party AI service
- Carrier handshake ML-KEM-1024 + X25519
- Blob sealing ChaCha20-Poly1305
- Carrier model sealed-blob relay
01 / THE THINKING STREAM — IN MOTION
Run it. The thinking streams first.
In developmentThe reasoning runs in the open. You keep the result.
ARTIFACT — VERIFY A NEW CONTACT
- Open the contact and read your six groups aloud, in order.
- Have them read theirs back. Every group must match, digit for digit.
- Mark the session verified. QERYX remembers the number you approved.
- If the number ever changes, you are told it was verified before — verify again before you trust.
Scripted demonstration of the Qaduceus surface — the reasoning and artifact above are authored copy, not a live model. In development: capabilities listed are the ones built, and no others.
Demo complete. The artifact is ready below the reasoning rail.
02 / THE DESIGN — LETTERED
Read the design, section by section.
In developmentThe visible thinking stream
Reasoning streams into an open rail as it runs. When a turn completes it folds to a disclosure you can reopen at any time — the record you audit is the record that ran.
- Turn law
- a completed turn is immutable — it is never rewritten after the fact
- Rail
- reasoning visible while it runs, foldable after
Workspace and artifacts
The answer is not a scroll of chat. Work lands as artifacts — plans, checklists, drafts — that you keep, reopen, and carry forward inside the workspace.
The relay cannot read your prompts
Conversations ride the same sealed-blob carrier model as your messages: hybrid ML-KEM-1024 + X25519 key agreement, ChaCha20-Poly1305 sealing. The relay holds ciphertext and opaque routing identifiers — prompts and outputs included.
Where inference runs
On your device by default. Heavier work runs on QERYX-operated hardware — your prompts never touch a third-party AI service.
The attested-enclave lane is the direction we are building toward: the enclave sentence ships when the attestation is real, and not before.
A separate surface, by doctrine
The messenger core carries no assistant and no scanning. Qaduceus is its own opt-in surface — your chats never feed it.
An assistant you can audit mid-thought.
- Reading your request — a verification plan.
- The Entangled pairing is the anchor.
- Drafting the checklist as an artifact.
The reasoning stream is the product
The path is the surface: you watch the thinking as it runs, then you keep the artifact it produced.
A completed turn never changes behind your back — what you audited is what happened.
03 / THE BUILT LIST — THE CONTRACT
No model numbers. One promise.
100%1
of capabilities listed on this page are built — the list is the contract
02
third-party AI services your prompts touch
| Surface | What is built | Framing |
|---|---|---|
| Thinking stream | visible reasoning rail; completed turns immutable | built |
| Workspace | chat workspace with artifacts you keep | built |
| Transport | sealed-blob carrier — ML-KEM-1024 + X25519, ChaCha20-Poly1305 | built |
| Inference locality | on-device by default; QERYX-operated hardware for heavier work | built |
| Attested enclave | GPU-attestation lane | direction — arrives when real |
| Model claims | none published | by design |
04 / THE LANE — WHAT IT NEVER TOUCHES
Trace the line Qaduceus never crosses.
The surfaces around it, with their own status
- Q-RATCHET · THE MESSENGER CORE STAYS CLEAN — No assistant, no scanning inside your chats: Qaduceus is a separate opt-in surface by doctrine.
- QLEAP · THREE HOPS, ZERO MEMORY — The post-quantum onion tunnel built to sit beneath everything you do on QERYX. In development — QLEAP arrives in a later update.
- CRYPTO-CORE · ONE RUST CORE — The same audited library seals conversations, messages, and files alike.
05 / THE VERDICT — CATEGORY COLUMNS
Set it against a cloud assistant and an on-device one.
| QERYX Qaduceus | Cloud AI assistant class | On-device assistant class | |
|---|---|---|---|
| Real workloads | |||
| Prompt privacy | Sealed carrier; QERYX-operated inference | Provider-readable, often retained | Private but capability-limited |
| Reasoning visibility | Full thinking stream | Hidden or summarized | Hidden |
| Vendor dependence | Sovereign stack | Third-party API | OS vendor |
| Operator subpoenaed | Sealed blobs — content requires breaking both X25519 and ML-KEM-1024 | Provider logs and prompts | Device seizure only |
| Capability honesty | In development: built-only list | Roadmap marketing | Not included |
06 / THE HARD QUESTIONS
Ask what “in development” rules out.
What does “in development” mean?
The page lists the capabilities that are built, and no others. Features arrive when they are real.
Can it read my messages?
No. Qaduceus is a separate opt-in surface; the messenger core carries no assistant and no scanning.
Where does it run?
On your device by default; heavier work runs on QERYX-operated hardware. Your prompts never touch a third-party AI service. The attested-enclave lane is a stated direction — it arrives when the attestation is real.
Is this a quantum AI?
No. Qaduceus is a classical assistant inside a post-quantum sealed transport. We publish exactly what is quantum in QERYX and what is not.
This is not QKD. Not quantum networking. Not quantum teleportation. We do not violate the no-communication theorem. Above an X25519 + ML-KEM-1024 floor that alone provides confidentiality, a session can fold a Tsirelson-bounded CHSH witness transcript into its key derivation — a deterministic classical co-possession witness, not physical entanglement; security never depends on it.
Why show the thinking?
An assistant you can audit mid-thought is the only kind that belongs in this stack. The reasoning stream is the product.
What can be handed over under subpoena?
Sealed blobs, same as messages. Reading conversation content requires breaking both X25519 and ML-KEM-1024.