Engagement

Start with a record you can disagree with.

An engagement moves from a bounded question to a first record, then widens only if reading that record together supports the next step.

Request access Inspect the demonstration

Sequence

Five decisions, each with a visible output.

The phases describe the work and the decision at each boundary. They do not imply a fixed duration or a standard commercial package.

Scope one entity

What you provide: One entity you already argue about, its current sources, the decision that depends on it, and who may read what.
What you receive: A written scope describing the first record, source permissions, reader clearance and deployment constraints.
Decision that follows: Whether this is the right bounded test and which evidence can be exchanged.

Deploy inside your perimeter

What you provide: An approved infrastructure boundary and your policies for sources, model routing, reader clearance and retention.
What you receive: A deployment inside that boundary, with one database for your organization and the agreed policies applied.
Decision that follows: Whether the deployment and evidence route satisfy your security and operating review.

Read the first record together

What you provide: The authorized sources for the scoped entity and the readers who will challenge the result.
What you receive: A record whose values, source excerpts, dates, disagreements and declared negatives can be inspected one by one.
Decision that follows: Which values stand, which need more evidence and whether the record is useful for the original decision.

Widen to the next entities

What you provide: The next entities and decisions, including any new source or clearance constraints.
What you receive: A proposed wider scope grounded in what the first record exposed, with changed policies stated in writing.
Decision that follows: Whether to expand, change the scope or stop at the first record.

Operate and export

What you provide: The people responsible for reading, reviewing and retaining the records under your policies.
What you receive: Records that can be revisited by date and an audit export for authorized readers.
Decision that follows: How the record enters your operating and audit process.

Written scope

What is fixed in writing before work starts.

The agreement names the scope and the allowed sources, who may read which evidence, retention, model routing and the commercial terms. These are conditions of the work, not assumptions left for the first record to expose.

Scope and sources: The first entity, decision and permitted private, licensed and public sources.
Reader clearance: Which readers may see each source and the values resting on it.
Retention and routing: How long evidence is retained and which model engines may see each material class.
Commercial terms: Agreed in writing during scoping. No price is published on this site.

See one before you ask for one.

A sample written scope and a sample audit export, both for the fictional Halden Therapeutics AG.

Sample, fictional data

Sample written scope

The document fixed in writing before work starts, for the fictional Halden Therapeutics AG: first record, permitted sources, reader clearance, deployment boundary, model routing, retention, export. No price or duration.

Download PDF

Sample, fictional data

Sample audit export

What an auditor receives for the same fictional record: each value with its excerpt, source, locator, dates, what it was chosen over and the reader clearance, plus declared negatives and blocked values.

Download PDF Download JSON Download CSV

Budget fit

Who this is for, and who it is not.

Who it is for: Organizations with a compliance, diligence or research-operations function that already spends on data and review.
Who it is not for: Individuals, one-off lookups, or teams looking for a self-serve SaaS seat.
Commercial terms: Fixed in the written scope before any work starts. No price is published on this site.

Data boundary

What we do not do.

We do not resell your data.
We do not train models on your material.
We do not keep a hosted copy of your record.

The deployment runs inside your infrastructure. Source, routing, clearance, retention and audit export follow your policies. Read the perimeter contract.

Before scoping

See the proposed record and its terms.

The four guarantees Security and data handling Methods

Enquiry

Bring one entity you already argue about.

Send the entity, the sources you fuse to describe it today and who may read which of them. We reply with what a first record would cover and what it would need from you.

Open a structured enquiry Contact and what happens next

Or write to [email protected] in your own words.