How Existential Is Built

This page is an orientation. It explains, in plain language, the shape of Existential: where your knowledge lives, how the Oracle works with it, and what happens to a note from the moment you save it.

The shape

Existential runs as a single local process on your own machine. That one process owns your stores, the Oracle (the constellation of agents that reads and reasons over your knowledge), the work that brings new notes into the system, and the schedule that runs your routines. You meet the Console and the Library in the browser, served by that same local process.

Nothing runs off your machine. Your knowledge stays with you.

Where your knowledge lives

Existential keeps its working memory across four kinds of storage. Each one is chosen for the kind of access it serves best.

• The relational spine is a small embedded database. It holds the record-keeping that ties everything else together: your conviction history, the state of your routines, your Console sessions, and the bookkeeping for every other store.
• The graph holds your documents, the passages within them, the concepts they touch, and the categories they fall under, with the connections among all of these. The Oracle's structural understanding of your knowledge lives here.
• The embedding store holds a mathematical fingerprint of each passage. It lets the Oracle find work by meaning rather than by exact words, and the Console draws on it for working memory as you talk.
• The filesystem holds your actual content: your vault on one side, and Existential's own internal files (configuration, logs, backups) on the other.

When Existential upgrades the way it stores things, it takes a full backup of every store before it begins, and it keeps the most recent backups on hand. Anything that can be rebuilt from your notes, such as the graph and the embeddings, can be wiped and regenerated safely. Anything learned over time, such as your conviction history, carries across every upgrade.

The Oracle

The Oracle is the constellation of agents that work with your knowledge on your behalf. Different agents do different jobs.

• The voice and the background mind are the two sides of the Oracle you meet in the Console. One holds the conversation with you. The other reasons in the background. They share a single model resident on your machine, which can think quickly or think more deeply depending on what the moment calls for.
• The conviction and synthesis agents produce the scores and the syntheses you see in your morning brief. Conviction is the Oracle's sense of how load-bearing a given passage is within your thinking, a measure of significance and never a claim about truth.
• A second opinion before anything personal stands between the Oracle and anything that touches its sense of who you are and what matters to you. A separate agent weighs in before such a change goes through. These operations fail closed: if the second opinion does not arrive, the change does not proceed.
• The observers run quietly on a schedule and keep an eye on the health of your knowledge and the system that holds it.
• How the Oracle revises its own assumptions is a loop that watches patterns over time and reviews the evidence behind its own assumptions, within set bounds. It is how the Oracle keeps from quietly drifting or calcifying, adjusting how it works as the evidence shifts.
• Insight after a Console session is a review the Oracle makes once a conversation ends. When something genuinely new surfaced, and only then, the Oracle writes that one insight into your notes, where it travels through the system like any other capture. Most of the time it writes nothing.

How a note travels through the system

When you save a capture, the note is written into your vault. Existential notices the new file and brings it into the system through a pipeline of twelve stages.

Along the way, the note is tidied into a consistent format, read for both its structure and its meaning, broken into concept-aware passages, given its mathematical fingerprint, and assembled with the details that describe it. For notes you authored yourself, the Oracle writes back the bracket links that connect the note into the rest of your knowledge. The note is then placed into a category and woven into the graph.

At the last stage, a conviction score lands on each passage, with a record kept in your conviction history. From that point on, the passage is visible everywhere the Library surfaces your knowledge: in search, in the unified view of a note, and in the synthesis of your morning brief.

A stage can fail. When one does, the note stops there and waits. The pipeline does not retry on its own; the note simply holds.

The morning brief and the evening close-out

Two routines bracket your day. The morning brief is the Oracle's synthesis of where your thinking stands and what may deserve your attention. The evening close-out is its reflective counterpart: it gathers the day's work and sets it into the longer arc of your thinking, so the morning brief and the close-out form two halves of one rhythm rather than a synthesis and an afterthought.

The calm surface and what runs beneath it

What you see in the Console and the Library tells a calm story about what the Oracle is doing. A great deal more happens beneath that surface, on a steady cadence, without asking for your attention. Anything Existential keeps out of view is kept out of view because it does not need to interrupt you. It all runs on your own machine, for you.