Methodology

Automatic public eligibility

An Event is public when it is not merged, retracted or disputed; it is in an emerging, active or resolved lifecycle; and at least one attached active Signal points to a public HTTP source registered as first-party.

This policy is deterministic and versioned as epoch-public-event-alpha-v1. It does not read the evaluation campaign, editorial Article status, X runs or distribution state.

What Epoch exposes

The public projection contains the Event ID, label, type, lifecycle, verification state, correlation confidence, event and observation times, resolved entities, and an allowlisted source trail. It excludes raw captures, model payloads, internal notes, evaluation rows and editorial workbench state.

Observed is not verified

First seen is when Epoch observed the source Signal. Event time is the time asserted by a source when one exists. Unverified means the Event has not passed a separate evidence review. Correlation confidence measures how firmly deterministic rules attached Signals to the same Event; it is not truth probability.

Editorial remains separate

An Article can cite zero, one or several Events. An Event needs no Article to be inspectable. Publishing, editing or removing an Article never changes Event identity, lifecycle or timestamps.

Corrections and removals

Disputed, retracted or merged-away Events leave the public projection on the next export. The newsroom retains its append-only history. Public timelines expose only safe observation metadata and source links.

Analytics boundary

Product request analytics stays at the public edge and is not imported into Radar or prospective-evaluation tables. Views, API traffic and referral data are never eligibility inputs and are not presented as campaign performance.