Docs
Reproducibility

Reproducibility

Data revisions, the provenance every response carries, and verifying which methodology release produced a number.

Every published assessment is a function of three things: a data revision, a lens and a methodology release. Name all three, and the platform computes the same result again, even after a source corrected or withdrew the data behind it.

Three time axes

AxisMeaningFixed by
Valid timeWhen something happened, or which period a value describesThe as-of date
Publication timeWhen a source made it knownThe as-of date
Transaction timeWhen the platform recorded itThe data revision

The as-of date cuts the first two axes: nothing dated or published after it is used. The data revision fixes the third: the records exactly as the platform held them after a given change.

Data revisions

Records are never updated or deleted in place. Each change set from a source becomes the next data revision, and the versions it replaces are retired, not removed, so every past revision stays readable in full. A delivery that changes nothing creates no revision.

GET /revisions pages through the revision log, newest first. Each entry states when the revision was recorded, the source and snapshot that produced it, and how many objects, links and observations changed. Send nextBefore back as before until it is null.

Provenance in every response

Every lens-scoped read model, except the object catalog, states what produced it:

FieldContent
revisionThe data revision the result was computed from
lensThe lens after defaults: asOf, window, themes, regions, actors and, when pinned, revision
methodologyThe release that computed it: version and fingerprint

Keep these three fields with every result you store, cite or hand to a decision.

Reading the past

  1. Pass asOf and revision on every read you want to keep. Without them, a read uses the latest data as of today.
  2. Store the methodology.version and methodology.fingerprint the response states.
  3. Read the same lens again later. For as long as that methodology release is deployed, the output is identical.
  4. To prove which method produced a number, verify the release's fingerprint, as Methodology shows.

To see what the platform knew on a past date, pin the revision that was current then: the revision log lists when each revision was recorded. Object properties, such as a sanctions regime's expiration, are read at the pinned revision; they are not reconstructed as of asOf.

Watchlists and alert read state belong to the caller and are always current. They never change an assessment or an alert's facts.

Statistics as released

Statistics carry their release dates. An assessment as of a date uses, for each period, the value that had been released by then, never a later revision of it. GET /indicators/{id}/observations returns the vintage current on the as-of date by default, and every vintage released by then with vintages=all, for revision analysis.