Documentation
User guide
What each screen shows, what a status means and how a question goes from a rule to an explained outcome.
Every record is a proposal in play points. No market is open, and the sites hold no price, no order and no wallet.
Catalogue and map
The catalogue lists the questions studied. Each record shows its status, its family, the source, the variable and its threshold, the freeze date and its limits.
A search field and two sets of filters, by family and by status, narrow the list. Each record links to its evidence file in the observatory.
The map and the globe locate the measurement places. A point marks a published station; an extent is an indicative window. Not every question has a place: a national or global statistic does not become a local point.
Images and location plans are context. They show where a measurement is made, not its value, and their date is not the date of the question.
Observatory and evidence files
The observatory holds one file per question: the question, the threshold, the sources, the rule, the deadline, the state of the evidence, the limits and the provenance.
A file can be exported as JSON. The export carries the text received from the catalogue, its SHA-256 fingerprint and the time the browser received it. The fingerprint covers the catalogue response, not a primary measurement archive.
Personal drafts stay in the storage of your browser. Saving a draft publishes neither a question nor evidence, and nothing is sent to a server.
The six statuses of a record
A status says how solid the evidence is today. It is declared by the catalogue; it is not an independent review.
| Status | Code | Meaning |
|---|---|---|
| Resolved from archive | resolu | Outcome already established by reading an archived file. |
| Open · play money | ouvert | The oracle can read the value at the freeze date. |
| Open · wording under review | reserve | The value can be read, but the question is weakened. |
| Historical replay | rejeu | Test on archives acquired after the events; no proof of past availability or predictive performance. |
gabarit | Rules and source access need qualification before opening. | |
| Not measurable as is | bloque | The oracle cannot establish it with its own means. |
Missing, doubtful or unvalidated data gives “unresolved”, never “no”.
From rule to resolution
The same four steps apply to every question.
Rule
Variable, unit, threshold, source and freeze date are written before the observation.
Freeze
On the set date, the file published by the source is archived with a fingerprint. That copy is the one that counts.
Resolution
The archived value is compared with the threshold: yes, no, or unresolved when the evidence is missing, doubtful or late.
Challenge
The file stays open to examination. A later revision by the producer does not rewrite the outcome.
The sites describe this cycle; they do not run it.
Historical replays
A replay applies a rule to the archive of a past period. It shows whether the rule can be computed and where it breaks.
The archives were acquired after the events, and the outcome was known before the rule was written. A replay is therefore neither a forecast nor a demonstration that the data was available at the time.
Replays are labelled as such in the catalogue and kept apart from open proposals.
What the sites do not do
- No price, no order, no wallet, no account.
- No audience measurement: preferences and drafts stay in the browser.
- No public API: the sites show a dated copy of the catalogue.
- No affiliation with the organisations cited: a source is quoted as published by its producer.