TRINITY · 1/fβTHE DÉJÀ VU EXPERIMENT
FREN

ONE SEQUENCE. A SECOND LOOK.

Déjà vu:
what if a sequence repeated?

Every fifteen minutes, Trinity examines a block of bits received from a public service. An experiment followed over time, with criteria fixed before the results.

View the experiment Read the protocol

16 KiB every 15 min · 30 days

HOLOGRAPHIC ILLUSTRATIONThe same cat. Two passes. One question.

THE STREAM / WHAT WAS RECEIVED

Receipts, then checks.

Reading the experiment report…

Receipts and tests will appear when a report is available.

Report published :

THE LATEST BLOCK

The trace of a receipt.

No received block has been published yet.

Cache and provider

Trace the delivery chain first.

A departure triggers a review of the delivered stream: cache, provider repetitions, transport and source. Request duration does not measure when the bits were generated.

Delivery evidence will appear with the first receipt.

THE TESTS / AT SEVERAL SCALES

A block. An hour. A day.

The same criteria apply to received blocks and complete UTC hours and days. Incomplete windows are not evaluated. Missing slots are not retried.

Tested windows will appear with their status and results.

THE LEADS / TO EXAMINE

When a criterion calls for a check.

An alert is a lead to review. Exact repetitions and statistical departures are shown with their delivery context.

Reading the campaign leads…

THE PROTOCOL / BEFORE OBSERVING

A fixed rule. Future data.

  1. Receive.

    One 16 KiB block per fifteen-minute slot. Its fingerprint, receipt time and cache evidence are retained; raw bits stay private.

  2. Compare.

    Four tests: the proportion of 0s and 1s, then disjoint pairs at lags of 1, 8 and 64 bits. A repetition is confirmed by an exact comparison of the entire block’s bytes, after fingerprint filtering.

  3. Check.

    A repeated sequence may come from a cache or the provider. Every lead needs that review before interpretation.

A global 1% error budget

Across the sealed campaign, under the assumption of independent, identically distributed uniform delivered bits. This rate concerns the protocol’s false alerts; it is not a probability of simulation.

View the manifest, seal and limits

The manifest and its fingerprint will be published with the campaign.

Report JSON

Observations concern the stream actually delivered to Trinity. This experiment is separate from the 1/fβ spectral analysis.

An interesting result starts with a verifiable trace.

Explore the investigations