Builtforthepartnobodyautomates.

Everything below describes behaviour, not a domain. That is deliberate — we would rather say less and have it be true than say more and have to walk it back at launch.

01

Three things, held together.

Each of these is achievable alone. The engineering problem is that they pull against each other.

01The model

Trained on the work, not the internet about the work

A domain model built on primary material and expert judgment rather than the second-hand summary of it that general corpora contain.

02The evidence layer

The chain is recorded, not reconstructed

Provenance is captured while the answer forms. Nothing is retrofitted afterwards, because a citation found after the fact is not evidence of anything.

03The adjudicator

A second process whose job is to disagree

It argues the other side. When it cannot be answered, the system escalates instead of resolving — the disagreement goes to the practitioner intact.

02

Where a decision actually goes.

The same four stages as the overview, with what each one refuses to do.

  1. 01

    Ingest

    Parses source material under a strict schema and records what it could not read.

    RefusesNever silently drops an input it failed to understand.

  2. 02

    Reason

    Works the problem in addressable stages, each one inspectable on its own.

    RefusesNever collapses the work into a single opaque pass.

  3. 03

    Adjudicate

    Runs an independent challenge against the conclusion and scores the disagreement.

    RefusesNever picks a side to produce a cleaner answer.

  4. 04

    Hand over

    Delivers conclusion, evidence, confidence and objection as one object.

    RefusesNever presents a conclusion without the means to reject it.

03

What we are not saying yet.

Not an oversight. These are the four things that would identify the field, and they stay closed until launch.

  • 01The industry we operate in
  • 02The institutions we are working with
  • 03The regulatory regime we are building against
  • 04The date we come out of stealth

Everything else on this site is accurate as written. When these open, nothing already published will need to change.

04

Where it runs.

Deployment posture, decided early because it constrains everything else.

Deployment
Single-tenant. Dedicated infrastructure per customer.
Data residency
Customer-selected region. Data does not leave it.
Training
No customer data enters any model we train or ship.
Retention
Configurable, floor of zero. Deletion is real deletion.
Audit
Full decision trace exportable, per request, indefinitely.
Access
Customer-held keys. We cannot read what we store for you.
Interface
API first. A review surface for practitioners on top of it.
Failure mode
Escalates to a human. Never degrades to a guess.

Be told first.

One message when we come out of stealth. Nothing else — no newsletter, no drip sequence, no sharing with anyone.

One email. No list sharing. Unsubscribe in a click.