Glossary · Data, licence and time

Licence tier

A licence tier is the classification carried by an individual fact that determines what may lawfully be done with it — stored, redistributed, resold, or only shown once to the caller who asked.
How to read this

The definition as the field writes it comes first, weaknesses and all. What Entity Bind does about it comes last, in its own paragraph, so you can take one without the other. Filed under data, licence and time.

On this page
the full definition

What licence tier means

A licence tier is a label carried by an individual fact, recording what its source permits: storage, redistribution, resale, or display to the caller and nothing more. It exists because company data arrives under wildly different terms. Companies House is published under the Open Government Licence, GLEIF under CC0, SEC EDGAR is US federal public domain, SIRENE is under Licence Ouverte 2.0. Other sources permit display but forbid warehousing, and others still are storable only while a commercial licence is live. A pipeline that mixes them and forgets which is which produces an asset nobody can safely resell.

The insight that makes this tractable is that the licence belongs on the fact rather than on the dataset. A golden record is assembled from facts of several origins; if the tier is carried per fact, the survivorship rules that pick a winning value and everything the system writes out can honour it automatically, and the resale-safe subset is derivable rather than negotiated.

Enforcement location is the question to ask a vendor. A licence honoured by a contract clause is honoured by whoever read the clause. A licence honoured by the write path is honoured by construction.

Entity Bind models four tiers — open, licensed, pass-through, and a provisional 'needs check' marker for terms that have been read and found genuinely ambiguous — and enforces three of them on the persistence layer: saving an entity carrying a pass-through fact raises before any write happens. Nothing is currently held under a commercial data licence, and 'needs check' is never treated as open in code. Resale rights are offered on the open-licensed subset only, on the plan that carries them.

in the running product

Where this shows up in Entity Bind

Three pages where this term stops being vocabulary and starts changing an answer, a payload or a price.

The fastest way past a definition is a file: which of your rows are the same company, which of your existing matches we would not have made, and what we could not decide.

Start free
see also

The terms next to this one

Each with its own sentence, because the next question is usually about the word beside this one.

Pass-through data

Pass-through data is material a system may return to the caller who asked for it but may never retain — the tier where the difference between showing and storing is contractual rather than stylistic.

Provenance

Provenance is the record of where each individual value came from — which source, retrieved when, effective when — attached to the value itself rather than to the dataset as a whole.

Reference data

Reference data is the slow-changing, externally defined data used to classify and identify things — registers, code lists, identifier schemes — as opposed to the transactional data that refers to it.

Golden record

A golden record is the single assembled view of an entity built by choosing one value per field from the records attached to it, ideally with the provenance of each choice carried alongside it.

Survivorship

Survivorship is the set of rules that picks which value wins, field by field, when the records in a cluster disagree.

Data, licence and time

The other 6 terms on this shelf

Facts have owners and dates. What may be stored, what may only be passed through, and what a date on a fact actually asserts.

evidence basis

Internal fixtures only. The historical 2026-08-29 per-tier recording covers 317 GB companies with identifier-rich arrivals seeding the catalogue first; the context tier includes country and registered-town prose. Its legacy replay has no full-prompt-verified calls and cannot certify current calibration. The September 5 CI reports cover 1,176 labelled pairs and 705 records over 250 companies using offline stubs. These are not independent customer holdouts or live production validation; the 99% minimum-input product target remains unmet. Scope is company and organisation identity only — not people, vessels, bank-account ownership, sanctions or emissions. Results may not be used for eligibility decisions about individuals, including employment, credit and tenancy.

the ask

Start with your own company records.

Create your workspace, verify your email and run your first company file. The Free plan needs no card. Create API keys in your workspace when you need an integration.

300 credits. No card.

For a guided review of your file, explore the Merge Safety Sprint →