Source boundaryAllowlisted
Only safe, current public-source metadata can enter the archive.
Unsafe destinations, replaced sources and protected artifacts are excluded.
01
The public report archive
Reporting records,with their evidence intact.
Browse a bounded public index of reporting events, official-report availability, verification, safe current source counts and revision state. Every record resolves to one stable event URL.
- Records in window
- 0
- Official reports available
- 0
- Projections marked stale
- 0
- Latest synchronization
- Not asserted
Event identity, schedule, availability, verification, safe-source count and revision. No protected report content is requested.
02
Ruled public index
One archive.Every state explicit.
Filter by company, reporting period or official-report availability. Dates, source counts, revisions and stale state remain visible in the index.
Query not verified
The live public index could not be loaded.
Public reporting data is not configured for this environment.
A failed read is not presented as a successful empty archive.
03
The anonymous boundary
Inspectable metadata.Protected work stays protected.
The archive uses the same constrained event and source projection as the public proof system. It links to the existing sample-report route instead of creating another reader.
AvailabilityExplicit
An unavailable official report remains unavailable.
The index does not infer a document from a schedule or a future reporting event.
FreshnessVisible
A stale projection is labelled rather than silently presented as current.
Query failure, successful emptiness and stale data remain distinct states.
Interrogate the evidence system
See how sourcesbecome report state.
The methodology explains verification, temporal precision, uncertainty, correction and revision. The source registry names the public evidence roles used across reporting events.