Coming soon · after the ontology, on purpose

Ask the operation
anything.

Once your business is nine named objects instead of forty tables, a question is just a query. No report builder, no ticket to whoever knows the schema, no waiting until Thursday. And nothing is written without your approval — Oracle reads the whole graph and proposes; you decide.

See the nine objects Start with a free scan
01 · What it does

One question, four objects, no SQL.

The question below touches Address, Unit, Event and Target. In a normal stack that is a data request with a two-week queue. Here it is a sentence, because the objects already exist and already know how they relate.

YOU ASK “Which addresses lost money last quarter, and was it cost or price?” IT RESOLVES ACROSS Address 318 installed sites Unit 1,204 deployed units Event append-only, 4 classes Target floor 18% · set by you AND ANSWERS 7 addresses below floor Rive-Sud · 14 units11.2% Laval Nord · 9 units13.8% Trois-Rivières · 6 units15.1% CAUSE, FROM THE EVENTS Freight up 19% since March. Price unchanged since 2024. cost, not price — 6 of 7 THEN PROPOSES — GATED PROPOSED, NOT DONE Reprice 29 units to clear the floor Recovers $41,300/yr Nothing has changed. Nothing will, until you approve it. Approve Decline
One sentence, four objects, an answer with its cause — and an action that sits behind your approval rather than in front of it.
02 · The rules

Reads everything. Writes nothing on its own.

What Oracle does
ReadsThe whole graph, in your own words. Every object, every event, every target — scoped to your workspace and nothing else.
WritesNothing without your approval. The same invariant that governs every module governs Oracle: it proposes with a number attached, you hold the decision, and no proposal that breaches a floor you set is ever offered.
ExtendsDefine a SKU, set a Target, save a recurring question, build a view. You personalise the system yourself instead of waiting for us to ship a bespoke feature.
CostsMetered in credits — work actually done, not logins. An allowance is included with every subscription.
CannotSee another operator's data, post to your accounting system unattended, or change a Target without recording who changed it and when.
Why credits and not seats. A seat prices the number of humans who log in. That stops describing anything the moment the work is being done by agents — and eventually by machines on your floor. Metering the work done is the only basis that still makes sense in five years.
03 · Why it is not first

A chat box over a mess is a demo.

We could ship this tomorrow and it would look extraordinary for ten minutes. Then someone would ask a question whose answer lives across six tables that disagree with each other, and it would confidently return something wrong.

The ontology first

Nine objects with defined relationships and one canonical value per field. Without that, a language model is guessing at your schema and dressing the guess in a sentence.

The events second

An append-only ledger with lineage back to the source record. “Why?” is the follow-up question to every answer, and it is unanswerable without it.

Oracle third

Which is where it is. Everything it will need is being built underneath it now, and the sequence is deliberate rather than a delay.

Sequencing this honestly costs us a good demo today and buys an answer you can act on later. That trade is the whole argument of the substrate.

The objects come first. Start there.

A free Margin Scan reads what you already have and returns one number. It is also how the first objects get built.

Get a Margin ScanSee the substrate