Anchor boundaries and clock uncertainty
Compare a declared existence boundary to the intended event, retaining uncertainty and refusing to infer delivery from a timestamp.
Evidence methods, not a provider certification. Authored examples and user-entered check states are not independently verified trading results.
Choose the deadline before interpreting the proof
The relevant deadline depends on the claim. A message said to exist before entry activation must be assessed against activation, not against a later favourable exit. A proof whose boundary precedes the exit can still be inadequate for the earlier entry assertion. Write the intended event, clock source, timezone and uncertainty before looking for a convenient comparison.
The chronology checker accepts a declared UTC boundary, a non-negative uncertainty allowance and a declared UTC deadline. It also records whether the input evidence is unperformed, pending or user-labelled checked. These are assumptions. The tool does not read a proof file, inspect a chain, synchronise a broker clock or interpret a blockchain timestamp on your behalf. Its result is a bounded comparison of supplied labels, not a provider verification.
Use intervals where the clock is uncertain
An exact-looking timestamp can still have source uncertainty. For this teaching convention, a boundary at 09:00:00Z with thirty seconds of symmetric uncertainty spans 08:59:30Z to 09:00:30Z. If the deadline is 09:01:00Z, the whole interval is strictly earlier. If the deadline is 09:00:15Z, the interval overlaps the event, so the example does not support a strict-before conclusion.
The symmetric interval is the checker convention, not a claim that every real timestamp has that error model. Actual attestation semantics and source clocks need their own interpretation. The tool allows at most one day of uncertainty and rejects unsupported dates or inconsistent field states. A real investigation can require asymmetric or non-numeric uncertainty; do not force it into this worksheet merely to obtain a green-looking result.
Equality is not strict precedence
A declared boundary equal to the deadline does not establish strictly before under this worksheet. The exact-boundary fixture therefore reports boundary_not_strictly_before, not success. If the entire entered interval is later than the event, the entered boundary does not support the intended before claim. That result does not prove the bytes were first created after the event; an upper-bound existence statement and a creation-time assertion are different objects.
The straddling fixture retains indeterminate status. This is a deliberate conservative boundary rule, not a measured signal failure. A narrower clock allowance could change the arithmetic comparison, but a reviewer needs evidence for that allowance. Editing assumptions after observing the desired result is not stronger chronology evidence. Keep the original comparison and any revised source interpretation as separate records.
Receipt, publication and subscriber access stay separate
A provider can retain bytes privately before publishing them. A subscriber can receive a message after publication because of transport, access, reading or platform delays. A broker can acknowledge or fill an order at another time again. A hash or existence attestation cannot collapse this sequence into one event. Request access and execution records when the claim concerns actionable delivery or account performance.
The practice packet deliberately leaves authentic receipt, delivery and broker evidence null. Its UTC strings are invented labels, not real operational observations. Exporting a comparison preserves what was entered, including the uncertainty and deadline. The result is useful as a review question: which source could justify these times, and does the claimed boundary actually address the event? It cannot supply missing source clocks.
Retain chronology without overstating precision
RFC 3339 provides a reference for timestamp representation; a syntactically valid string is not evidence that an event occurred at that instant. The checker uses an explicit restricted UTC profile with seconds and optional milliseconds, rejecting offset forms and leap seconds rather than claiming to implement every possible representation. Its supported date window and limits are stated on the tool page.
For a public finding, report the event and uncertainty alongside the conclusion. A bare before-outcome badge hides too much. Link the exact record, proof-state assessment and independent transcript if available. If the transcript is absent, say that the worksheet compared supplied labels only. Financial validation, full-period completeness and subscriber receipt remain separate requirements even when the arithmetic interval lies wholly before the selected deadline.
Mechanism and source references
Mechanism references are not provider certifications. The new editorial examples are authored exercises; no independent financial review was performed.
Inspect the working packet
Eight originals, four discrepancy variants and six chronology cases