About the archive

An independent record of disputed system behavior

Founded in 2007, the archive compares reports that would otherwise remain isolated anecdotes and preserves technical explanations alongside Protocol interpretations.

Editorial purpose

The project provides a stable vocabulary, permanent case identifiers and a repeatable assessment method. Its purpose is comparison: what happened, what the user did, what returned and what conventional mechanism could explain it.

Editorial independence

The archive is not affiliated with a platform, vendor or academic institution. Vendor names are withheld when identification would add little to the technical description or could expose a reporter.

Limits

The archive does not claim that all listed systems share an implementation. Similar behavior can arise from unrelated software design, stale state, profile synchronization or common optimization methods.

Archive governance

Small review group, documented decisions

Intake editorNormalizes dates, service type and the reported sequence.
Technical reviewerIdentifies conventional mechanisms and tests internal consistency.
Publication reviewerAssigns status and records the last review date.

Start with the definitions

Read the model before the cases

The Protocol