Three boxes. That is the whole system.
You're on the technical page. If you're an engineer, a sovereign builder, a security researcher, or a journalist who needs the receipts, you're in the right place.
If you're a tired professional who came here from the product page, you can close the tab and pick this up later. The product page already told you what the product does. This page tells you how.
Where the data lives.
Your machine
The assistant thinks, remembers, hears, speaks, and acts locally. Your voice and your conversations never leave the disk unless you send them somewhere yourself.
The cloud
A small set of edges that go to the cloud, only when a specific job needs it: complex reasoning the local model can't handle, a license check, a software update, and outbound email if and when you send one.
Third-party services
Payment and email delivery. We don't write the payment processor or the email sender; we use the standard ones.
Six times a day, the assistant does work on your machine.
When you dictate to the assistant
You say something. The product hears it on your laptop. The transcribed text is processed by the local brain. Nothing is sent to the cloud for transcription. The cloud never hears your voice.
Local voiceWhen the assistant remembers something
You say I got promoted to manager. The episode is saved on your machine, in your memory store. Later, when you say what did I tell you about my job?, the assistant recalls it from local memory, weights it by source, and answers.
Local memoryWhen the assistant reads a file
You ask the assistant to read the binder. The hands process asks for the grant. You grant it. The binder is read. The audit ledger records what was read, when, and from which folder. The binder never left the disk.
Local hands, with your permissionWhen the assistant thinks hard
You ask a question the local model can't answer well on its own. The brain routes to the cloud model. The cloud model sees the question, the retrieved context, and the answer — not your memory outside the scope of the question, and nothing stored beyond the request lifecycle.
Local brain, sometimes cloudWhen you send an email
The assistant drafts it. The assistant asks for confirmation before sending. You confirm. The email is sent through a relay we run, which uses a standard email delivery service. The audit ledger records the send.
Hands and email relay, with confirmationWhen you turn the hardware toggle off
The microphone is cut at the device level. The telemetry that the cloud might receive is cut at the source. The assistant continues to work in text only. The cloud sees that the toggle is off and respects it.
You, in controlFive layers.
Working
What's happening right now. The current conversation and the immediate task. Released when the conversation is done — unless something earns a longer life.
Episodic
What just happened. Conversations, files touched, requests made. Each an episode with a moment, an outcome, and a confidence weight.
Semantic
Durable facts about you and your work, promoted from episodic memory because you kept returning to them.
Procedural
Learned skills. When you ask for a summary of a deposition exhibit, you want the page numbers. Each skill is a pattern, stored on your machine.
Persona
Who you are, over time. Your tone, your preferences, your sense of a good answer. Persona is yours to change, rewrite, or ask the assistant to forget.
The layers talk through a quiet consolidation step — call it a sleep cycle. Recurring episodes become semantic facts; recurring patterns become procedures; recurring patterns-of-you become persona. A fact that recurs three times in a week is a fact worth keeping. The system does not grow without you.
Three controls. They are non-negotiable.
The hardware toggle
A physical switch that cuts the microphone and device-level telemetry at the source. Toggle off, the product works in text only. The cloud respects the off state.
The kill switch
A button, visible at any time, that stops outbound action. No email, no posts, no writes outside your machine. The local brain continues to think. The hands will not move.
The audit ledger
A live panel that records what the assistant has read, written, and proposed to send. Yours to read, export, and clear. Clear happens on your machine, never on the cloud.
The kill switch is the last to fail. Sovereignty beats autonomy. Every time.
You download the installer. You open it. You give your email. The product verifies the license and opens. Activation takes about nine seconds. You can start typing or talking immediately.
We don't tie the license to your name unless you tell us your name. We don't use the license to track you. We can revoke a license; we cannot read the assistant's memory of your work.
What we ship with confidence, and what we're hardening.
Solid
- Memory: the local-only store has not lost a byte in production through v1.0.x
- Auth: signed license, machine fingerprint, offline grace
- Audit ledger: append-only, scoped per user, visible
- Local voice pipeline: no cloud round-trip
Watch
- The anti-tamper guard — working by design; we'll tell you if that changes
- Daily backups — you set the cadence, the system honors it
- The signed installer — self-signed today; vendor-signed is what to watch for
Tension
- Installer pipeline cutover — the next installer starts faster and installs quieter
- SmartScreen friction — goes away with vendor signing, targeted v1.1
- The manual license form — fixed or removed in v1.0.5; you should know it exists
Decisions open. Published.
- License grace window — 14 days today, kept at the default for now.
- Lapse behavior — degrade to text, memory and files accessible. Locked in.
- Cross-platform support — exploration only. We don't promise macOS or Linux yet.
- Proactive suggestions — not enabled by default, and not without your opt-in.
Plain English for the words we use.
Audit ledger. A live log of what the assistant has read, written, and proposed to send. It lives on your machine.
Consolidation ("sleep cycle"). The quiet background step that promotes recurring episodes to facts, patterns to procedures, habits to persona.
Fingerprint (license). A one-way summary of your hardware. Not your name, not your email. Used only to bind the license to the machine.
Jade Seal. The license and integrity service. Signs licenses, checks signatures. Sees only what's required to verify a license.
Kill switch. Stops outbound action. Local brain keeps thinking. Hands stop moving. Last to fail, by design.
Persona. Long-lived sense of you, built from how you talk to the assistant. Yours to change.
Procedural. Learned skills — patterns the assistant applies without asking again.
Sovereignty. You decide what runs, what listens, what gets sent out. Hardware toggle + kill switch + audit ledger.