Public evidence receipt

Signal, then proof.

This page is a stable, shareable explanation of one public Codex reset signal. It keeps the readable record and the machine-verifiable receipt together.

Early public signal: Community reset corroboration

A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.

Public source time: · Confidence: 72%

Want the next verified public signal?

Keep this receipt as the proof for the current event, then join the one-email alert for the next confirmed public signal. No daily digest and no Codex login.

Get the next confirmed alert ->

Source time

. This is the timestamp recorded from the public signal.

First observed

(timing sample not eligible)

Confirmation state

Not independently confirmed; treat this as an early public signal. Public evidence is not personal account telemetry.

Claim scope

broad public. The public source makes a broad or shared-scope claim; this does not prove every account changed.

Event type

unknown. The public record does not establish the event type; do not use it for cadence calculations.

Integrity receipt

sha256:f5e30829abeea9198188f10b9b6cc3633d656a3b5b31ffa85d9c39ca1898ae6e

The receipt proves the integrity of this public record, not the private state of an individual account.

History check

Checking first-observed receipt….

The public API will show the first-observed record when one is available.

Community outcome pulse

Loading the optional event-level community pulse…

Source provenance

This record is classified as Corroborating public signal. Official service status is context only, and anonymous community observations remain unverified. ResetPulse only counts distinct origins accepted through its evidence ledger; mirrors, embedded posts, and shared-origin trackers are not treated as separate evidence.

Use this evidence correctly

A public signal can arrive before or after a particular plan, region, or account changes. Compare it with your own Codex UI, keep the relevant timezone and limit type, and do not infer a universal reset from one public event.

Machine-readable record

Open the JSON receipt for the canonical record, ETag, and evidence boundary. Verify this receipt in your browser before sharing it. Return to the live timeline for the surrounding history.

Propagation trace

See the public stages from source time to collector observation to thresholded account/plan outcomes. The trace publishes aggregates only; raw observations and private account data remain unavailable.

Open propagation trace (readable) · Open JSON trace · Open trace schema