Evidence capture

Evidence capture is the module that turns the evidence log into something a supervisor can read. It collects what each storage provider's own logs, the public registry and the customer's signing service recorded about the scope's entries, reconciles those records with the SDK's observations line by line, and generates the provider access reconciliation and the supervisory extracts.

The module is licensed to enterprise customers and is not part of the SDK. What is public is the format of what it produces, frozen in the SDK specification, so that the standalone verifier checks every artefact with no SDK, no API and no account.

What the SDK exposes for it

SignedUrlProvider reports a receipt per object operation with the provider request ids, ETag, version id and content length, and every request to the signing service carries a correlation id. FilePipeline, verifyFileShardHealth and ShardRepairManager accept observers that are awaited after each shard operation and each registry submission. The @dataprism/sdk/format module defines dataprism.provider-access-reconciliation.v1, dataprism.supervisory-extract.v1, dataprism.artefact-signature.v1 and dataprism.qualified-timestamp.v1, with parsers, canonicalisation and hashes.

What a reconciliation establishes

Every line rests on entries of one verified, hash-chained evidence period, named by sequence and hash. A matched line was seen both by the SDK or the registry and by an independent record, and states how it was matched: provider request id, correlation id, time window or transaction hash. The identity binding of a line says whether the identity the provider or the registry recorded equals the identity declared on the customer side, and gives the reason when that cannot be said. Each time on a line is labelled with the source that observed it.

What it does not establish

That any source delivered every event. A provider-only or sdk-only line is a gap as observed, and each source carries a coverage label. Established time: a qualified timestamp is stored beside the artefact and is not verified by it. The natural person behind a provider principal when no signing service record exists. And no artefact states that an entity complies with, is exempt from or falls within the scope of any regulation. The extracts name the article and state what it says.

Supervisory extracts

Four extracts exist, each a selection over one reconciliation: the DORA incident chronology, the DORA third-party annex, the MiCA record-keeping extract and the MiCA custody extract. Every citation carries the date it was last read against the Official Journal text, or null when that reading has not happened yet, and the rendering prints that state next to the citation.