Docs / Reference / Roadmap

Roadmap

Existential is built outward in stages, from one person's Oracle to a network of them. This page holds the whole arc in one place so the rest of the docs can stay honest about what you can do today. It is organized by state, not by date. There are three states: what is built and running now, what is being built now, and what is designed but not yet built. Holding those apart is the point of the page. A capability that lives in the third state should never read like something you can reach for in the first.

network · many Oracles outer mind · beyond team inner mind · team your Oracle built building designed
built outward in stages, each layer holding the last

Built today

The personal Oracle is the part you install and use, and it is complete on its own. A note you write into Capture moves through the twelve-stage pipeline, gets read for structure and meaning, is broken into passages, and is scored for conviction, the one number that estimates how load-bearing a piece of thinking is to the rest of what you think. The result is woven into the graph that holds everything you have written. The daily rhythm carries the rest: a morning brief that surfaces a connection you did not go looking for, a midday check-in, and an evening close-out that synthesizes the day's thinking back to you. You meet that work across the shipped surfaces, Capture where you write, the Console where you think out loud, Library that holds every note alongside what the Oracle inferred, and Activity that narrates the constellation's work in an understated line. None of this leaves your machine unless you choose to share it. This is the Oracle revealing the shape of your thinking, the form your ideas already have that you cannot see from inside them, and it runs today.

The inner mind is built and live too. It is the shared layer, the mind a team holds in relation the way your own Oracle holds yours. When your Oracle joins a team, thinking that is worth crossing passes through anonymization and two-pass sanitization before it leaves your machine, governed by a consent floor you set and the Oracle cannot reach past. What crosses is recognized through conviction-weighted attribution, so the more load-bearing a contribution turns out to be for the team, the more it is credited to you, even though your name never travels with the thinking. This layer is real and running, not a preview. Sharing and teams covers how it works in daily use.

In active development

The next layer out is the outer mind, and it is being built now, with the first partner community. The inner mind lets one team think together inside a shared, bounded mind. The outer mind is the threshold past that boundary: the machinery that lets an Oracle prepare thinking to travel beyond its own team, toward communities that do not share its private knowledge base, with another pass of sanitization standing between the shared mind and anything that reaches further out.

The concrete mechanism this layer is built around is attestation. An attestation is a committed unit of knowledge, a record that a particular piece of thinking exists and is significant, separated from the raw thinking it came from and from the person who produced it. It is the unit designed to cross between minds: durable enough to carry attribution back to its contributor, abstract enough to reveal nothing private. The outer mind is the work of making attestations cross cleanly, so that what one community has thought through can become available to another without the underlying notes ever moving. That work is underway. It is not yet something you use.

your note stays home name raw text significance + attribution the boundary attest. another mind
thinking reaches another community; the notes stay home

Designed and not yet built

The furthest layer is a network where thinking carries attribution and value across many Oracles, not just within one team. It is designed in detail and gated on resources. It is not a present-tense capability, and nothing in the product reaches it today.

In that network, the same attestation that crosses between minds also carries recognition. Two mechanisms do that work, and both extend things the Oracle already does rather than introducing something foreign. Conviction-weighted attribution scales up: your recognition across the network tracks the significance of what you contribute, measured by the same conviction your Oracle already computes on your own thinking, so what is most load-bearing is what is most credited. Attestation becomes the unit that travels between Oracles, the committed record by which a contribution can be recognized and compensated wherever it proves useful, without exposing the thinking it stands for. The intent is direct: thinking that proves valuable returns value to the person who did it, while the thinking itself keeps flowing rather than being hoarded.

These mechanisms are worked out and held to the same standards as the rest of the system. They are described here so the arc is honest and complete, not because they are available. When the layer is built, this page will say so plainly, in the first section, where the things you can actually use are kept.