Methodology

How reports are classified

Documentation quality and pattern fit are assessed separately. A well-documented event can still be an unlikely Protocol case.

Review sequence

Four passes before publication

RecordDates, platform, sequence and available evidence are normalized.
ChallengeA conventional technical cause is identified for comparison.
ScoreEvidence Strength and Protocol Fit are assessed independently.
PublishThe case is reviewed, withheld or rejected with its original ID retained.

Outcome

Classification scale

Confirmed Pattern: The behavior repeated under recorded conditions. This does not establish deliberate manipulation.
Strong: Several features match the pattern, while a conventional explanation remains possible.
Probable: The report partially matches the pattern, but controlled repetition is incomplete.
Inconclusive: The available sequence does not support a reliable classification.
Unlikely or Rejected: A technical explanation is more plausible or reproduces the reported effect.

Measure one

Evidence Strength

Rates documentation: source continuity, screenshots or logs, repeat attempts and corroborating accounts.

LowModerateHigh

Measure two

Protocol Fit

Rates correspondence with the defined sequence after technical alternatives have been considered.

LowModerateHigh

Why rejected cases remain visible

A credible archive must preserve findings that argue against its own premise. Rejected cases show where ordinary synchronization, caching, validation or recommendation logic provides a better explanation.