Carry verified source relationships through the full reporting event.
Public output receives only approved source metadata and safe destinations.
Reporting-event workflow
Follow a reporting event from discovery through verification, acquisition, protected analysis, conditional live evidence, controlled delivery and revision.
The event identity persists while evidence coverage and publication state change.
The operational sequence
Each stage changes what is known about the same event. The sequence keeps source coverage, uncertainty and publication state explicit.
Associate a candidate release, notice, presentation, call or transcript with the reporting event. Discovery records a possibility; it does not certify the source.
Check source identity, destination, event timing and replacement state before treating the candidate as current evidence.
Retain an available source with its type, location and acquisition context. Inaccessible material remains a visible coverage gap.
Organize evidence inside the protected workspace, keeping comparison limits, uncertainty and unresolved questions attached to the event.
When a presentation, call, webcast, transcript or Q&A is available, add it as conditional evidence without implying that every event has the same coverage.
Publish a public-safe report only when its publication state permits. Otherwise, the event continues to show an honest unavailable or incomplete state.
Incorporate corrected or newly available evidence into the current revision while preserving the source and report lineage that preceded it.
Conditional source paths
A written release and a live call do not have identical availability or authority. Their paths remain separate until the evidence returns to the reporting event.
Official release or exchange notice
Presentation or supporting document, when available
Source-linked evidence coverage
Call or webcast destination
Transcript or prepared remarks
Q&A evidence with source context
Delivery boundary
The workflow ends in a controlled public projection, not a copy of the protected research workspace.
Carry verified source relationships through the full reporting event.
Public output receives only approved source metadata and safe destinations.
Use written and live evidence together when both are available.
Conditional branches remain visibly incomplete when a call, transcript or Q&A is absent.
Update the delivered report as corrected evidence arrives.
Revision and provenance state remain public-safe; protected intermediate work does not cross the boundary.
Continue with the evidence
Public reports use stable event destinations and show availability, source coverage and revision state without exposing protected analysis.