Skip to content
A system of record for fused private and public information

A kernel of truth for organizations that fuse private and public information.

A system of record for the facts your organization has to defend: one canonical record per real thing, a cited, verbatim, dated source behind every value, unknowns declared rather than left blank, and any past state reproducible on demand.

We reply within two business days.

Who it is for
Compliance, diligence and research-operations leads in regulated organizations, in pharmaceuticals, financial services and four other sectors.
What you get
A deployed record that fuses your private records with public sources, inside your perimeter, with one database for your organization. Sources, model routing, reader clearance and retention are your policies.
How it starts
With one entity you already argue about. A written scope fixes sources, readers and retention; you read the first record together before deciding anything wider (how an engagement works).
Budget fit
For organizations that already spend on data and review. Not for individuals, one-off lookups or a self-serve seat. Commercial terms are fixed in the written scope before any work starts.
A stack of nine aligned clear glass plates lying flat on a white surface, seen from a low angle so the stacked edges read as fine parallel lines, with one plate in the middle of the stack showing a deep cobalt blue edge.
Nine readings of the same thing, kept rather than collapsed. The record shows you which one a value came from, and leaves the other eight where a reader who disagrees can find them.

A record, as the person acting on it sees it

Halden Therapeutics is fictional. The behaviour is not: select a value, or replay the record at an earlier date.

record

Halden Therapeutics AG

Replay
kindCompanyanchorhaldentx.comreaderResearch analyst, public-sources clearance4 cited1 not found1 blocked
values4 changed between the two dates
evidence14 March 2026

Lead program

HLD-204

“Following the January reprioritisation, HLD-204 is our lead candidate and our principal development priority.”
Source
Corporate presentation, February 2026
Read at
slide 4
Observed
11 March 2026

chosen over

  • HLD-118observed 11 March 2026

    haldentx.com/pipeline, page not revised since August 2025

    A dated presentation outranks an unrevised web page.

The record as it stood on 14 March 2026. After the January reprioritisation and the change of chief executive.↑↓ values←→ dates

In production in two sectors

Deployed inside customer infrastructure, against live private and public sources, with their own policies.

6,000+ identity decisions by rule, none reversed

More than six thousand decisions about whether two records describe one real thing, made by rule. None has since been reversed. The count includes evaluation runs and has not been independently audited (counting rule).

Every value cites a retained source, verbatim

There is no path by which a value reaches a reader without the sentence, the locator and the date it was read.

The sequence

How a value earns its place

Four properties, in order. Each one is a thing you can check on any value the system shows you, not a description of how the system is built.

How the product works
  1. 1

    Source retained

    The document a value was read from is kept as it was read, with the moment it was fetched.

    A value whose source has since moved, changed or vanished can still be defended.

  2. 2

    Excerpt cited

    The value points at the sentence it came from, quoted verbatim, with its page or address and the date it was observed.

    A paraphrase is not a citation and does not count as one.

  3. 3

    Conflict shown

    Sources that disagree are both kept. The record shows the value it carries, what that value was chosen over, and on what grounds.

    Disagreement is reported, never averaged away or silently dropped.

  4. 4

    State replayable

    Every value carries the date it was observed and the date it entered the record, and nothing is overwritten.

    Any past state of the record can be reproduced and read again.

A brushed aluminium block lying on a pale surface with a single deep cobalt blue strip inlaid flush along its full length.
The four properties run the length of a value the way the inlay runs the length of the block. A value that has three of them is not three quarters defensible; it is undefended at the point where the fourth was needed.

The four guarantees

What the record promises a reader

These are the whole contract. Everything else the system does exists to make one of them true.

Each guarantee in depth

One canonical record per real thing

A company, a person, a facility, a program, a contract: each has exactly one record, whatever it has been called. Former names are kept. Records that relate are linked rather than folded together, because merging two real things falsifies both.

exampleA supplier that changed its name twice keeps one identifier; the two former names still resolve to it.

A cited, verbatim, dated source behind every value

Every value points at the sentence it was read from, quoted word for word, with the page or address, the date it was observed, and a retained copy of the document. A paraphrase is not a citation and is not accepted as one.

exampleA phase reads Phase 2 because a registry record version 9, read on 11 March 2026, says so in those words.

Unknowns declared, never blank

Where there is no evidence, the record says so in words: not found, blocked, or not applicable, each with a reason and the record of what was searched and when. An empty cell is never emitted, because a blank reads as a negative.

exampleA readout date with no published source reads not found, and lists the four sources searched and the dates.

Any past state reproducible

Nothing is overwritten. Every value carries the date it was observed and the date it entered the record, so the record as it stood on any past day can be reproduced and read again, together with the sources that supported it that day.

exampleThe brief you sent in March can be reproduced in September, with the source each line rested on then.

Deployment

Inside your perimeter

The kernel runs on your infrastructure, with one database per organization. Nothing about your sources, your readers or your retention is decided outside the boundary you draw.

Sources
Which documents, feeds and systems may be read at all, and under what licence.
Model routing
Which engines are permitted to see which material, stated as a policy rather than settled per job.
Reader clearance
Who may see which source. A value a reader is not cleared for is labelled blocked, never silently dropped.
Retention
How long a retained document and its derived values are kept, and what happens at the end of that period.
A rectilinear pale stone enclosure seen from above with a single opening in one wall and one cobalt blue block at its centre.

Every value exports with its chain of custody: the source, the excerpt, the locator and the dates, in a form an auditor can read without access to the system.

your infrastructurePrivate sourcescontracts, filings, internal systemsLicensed feedssubscription data under your licencePublic recordsregistries, regulators, publicationspolicies you setSourceswhat may be readModel routingwhich engines see whatReader clearancewho may see which sourceRetentionhow long anything is keptReliable Contextone database per organizationExport: chain of custodyevery value leaves with its source, its excerpt and its datesauditors, regulators,counterparties
Sources enter through policies you set. The kernel holds one database for your organization. Values leave carrying the evidence behind them.

Research

We publish measurements, including failures.

The problems this product is built on are open research problems. We would rather be corrected in public than be quietly wrong in a customer’s file.

Research program

open problems

  • Deciding that two records describe one real thing from evidence, without a similarity threshold standing in for a judgement.
  • Measuring whether a declared unknown was correctly declared, when the ground truth is also an absence.
  • Detecting the moment a retained source stops supporting the value that was read from it.
  • Comparing sources that disagree without a standing ladder that encodes one analyst's prejudices as a rule.
  • Evaluating a fused record end to end, when no public benchmark contains the private half of the evidence.

reading the literature

  • PROV-DM: The PROV Data ModelW3C Recommendation, 30 April 2013
  • Knowledge Vault: A Web-Scale Approach to Probabilistic Knowledge FusionDong, Gabrilovich, Heitz, Horn, Lao, Murphy, Strohmann, Sun and Zhang. KDD 2014
  • A Survey on Truth DiscoveryLi, Gao, Meng, Li, Su, Zhao, Fan and Han. SIGKDD Explorations 17(2), 2016
  • Measuring Attribution in Natural Language Generation ModelsRashkin, Nikolaev, Lamm, Aroyo, Collins, Das, Petrov, Tomar, Turc and Reitter. 2021

work with us

  • Data access under agreementEvaluation sets with their evidence, for groups working on provenance, fusion or attribution.
  • Co-authorship on evaluationsWe publish the protocol before the result, and the result whichever way it goes.
  • How to citeA BibTeX entry for the position paper is on the research page.

Further reading

Articles on this page’s subject.

The research library

See a record defend itself.

Bring one entity you already argue about internally. We will show you what it looks like when every value on it carries its source.