What the public record carried about a named asset as of a fixed date — field by field, each cell Sourced, Derived or Absent, with the primary documents catalogued and, for the assets below, preserved as byte-hashed copies shipped with this site. It records resolved public fact at a date. It is not an opinion on any dispute, not a valuation, not a prediction, and not testimony.
Why this cannot be assembled after the fact. The record depends on a retained, versioned, append-only trail kept contemporaneously under a published standard: dated cells, a correction log, a right-of-reply record, and preserved source bytes. A compilation made later from today's web is a description of today. The date on this record is the date the platform's own state carried, and the build and dataset versions that produced it are stated on its face.
Six assets carry a complete preserved-document set; their record depth ranges from about 6 to about 55 cells and the count is shown on every record. Two of the six are in an interest jurisdiction and are published as data-layer compilations only, not as engagements. Other assets can be recorded from the feeds, without the byte-hashed exhibit layer.
Loading…
What a delivered record adds
The page below is the record's content, live from the feeds. A delivered record additionally carries: the exhibits themselves (the preserved documents, by hash); the correction-SLA record and right-of-reply record for the period covered; the retained dataset versions the record was assembled from; and a signed statement of editorial responsibility. Delivery is a project engagement.
Scope limit, on the face of this offering: records touching the DRC, Rwanda or the Great Lakes / conflict-minerals complex are data-layer factual compilations only, and any engagement touching that region requires a fresh, explicit conflict-of-interest ruling by the editorial-responsibility-holder before it is accepted. See the Independence Policy.