Draft in progress. DeepGravity is in development, and this manual is being written as the system is built. The sections below are the finished sections of the draft. Further sections — what DeepGravity is in plain words, the box, where your data lives, your braid, and getting started — are still to come and will be added here as they are finished.
1. Your data is encrypted, and only you can unlock it
Your conversations are encrypted with a passphrase only you know. If someone copies the files, they cannot open them without it.
That matters because of what a passphrase is. It is something you know, not something you are. The law treats those differently. A fingerprint or a face is physical, like a key. With a warrant, you can be made to give it up. A passphrase is testimony about what you know, and the Fifth Amendment protection against self-incrimination makes compelling it much harder. It is not absolute, courts have split on it, but it is a real protection, not a loophole.
That is why DeepGravity uses a passphrase, and only a passphrase, to unlock your data. No fingerprint or face unlock standing in for it.
Encryption is on by default, at rest, for ordinary operations. Conversations are encrypted, period. There is no level to pick and no opt-out. Created artifacts, like markdown files and images, are a separate decision and stay deferred for now.
The passphrase gate is the first thing that happens on login, before the screen renders and before any module mounts. Credentials live only inside the encrypted keystore, never plaintext in config.
Open question, not yet decided: What happens if you lose your passphrase? This needs a decided answer before it can be stated as fact, and it has not been decided yet.
8. The background service: remembering, categorizing, and the one unlock
DeepGravity has a part that works when you are not talking to it. It starts by itself when the box starts, and its job is everything that happens to your conversations after you have them.
It remembers. Each conversation is written into your encrypted record and into your braid, so the history your engine can draw on is yours and stays yours. It categorizes: every turn gets its privacy tag, and the classifier can raise a turn to NT when it matches the boundary descriptions you approved. It answers: when an engine asks for relevant pieces of your past conversations, this service is what looks them up and hands them over — and it enforces the tags while doing it, so a cloud engine never receives NT or NK material, and your local engine receives everything. And it compacts: long conversations are summarized into the braid, so their substance is kept without their bulk.
It does not depend on the front door. The gate on port 80 is one way in; the background service is not behind it. The door can be closed and the remembering still runs.
The one thing it needs from you is your passphrase, once, on its unlock page. You reach that page through DeepGravity itself — on this box, the dev surface you already use (127.0.0.1:3889), at its background-service address, /dg-daemon/. The service has no page of its own on the network; the chat surface carries you to it. The first time, that page is where your keystore is created and your recovery phrase is shown. After that, entering your passphrase there unlocks the service, and that single unlock is what arms everything above: remembering, categorizing, retrieval, compaction, and any import of older conversations waiting to be committed.
Your key lives only in the service’s memory. It is never written to disk. If the service restarts, or the box reboots, or you lock it from its page, the key is gone and the page asks for your passphrase again. That is the design, not a fault: there is nothing on the disk for anyone to take.
What you see depends on which state it is in. Locked: the page shows the passphrase form; your conversations still happen in the chat screen, but nothing new is remembered or categorized, and when an engine asks for your history it gets nothing back. Unlocked: the page says the background service is running and the keystore is unlocked, and from that moment your conversations land in your record and your braid as you have them.