GeoOracleDocs

DOCUMENTATION

GeoOracle documentation

GeoOracle studies questions about climate, water and agriculture that a public source can settle: a rule written in advance, a value read on a published source at a set date, and a file that explains the outcome. These pages describe the demonstrator: what it does and how to read it.

Status

Demonstrator in development; nothing is in production. The records are proposals in play points, not open markets. The catalogue is a research file, not primary evidence.

Quickstart

Three places to start. Nothing to install.

  1. Browse the catalogue

    Pick a question and read its status, its source, its threshold and its limits.

  2. Find it on the map

    See where each measurement is made, on the globe or on the detailed map.

  3. Open its evidence file

    The observatory shows the rule, the provenance and the limits of each question.

Project status

A complete demonstrator, not yet a service.

On 16 November 2026, GeoOracle is a demonstrator. Nothing is in production.

3
sites: catalogue and map, observatory, documentation
4
languages for the interface and the content
0
real transactions: play points only

Catalogue and map

The questions, their sources and their limits; a globe and a detailed map of the measurement places.

Evidence observatory

One file per question: rule, provenance, export and local drafts.

Each component has its tests; they validate neither a scientific result nor profitability.

The need

The data exists. The decision still needs a basis.

Gathering sources, finding the right version and understanding exceptions take time. GeoOracle aims to provide a shared file that anyone can examine and challenge.

Professional teams

Support recurring decisions and reduce verification work.

Communities and organisations

Track commitments with understandable criteria and accessible documents.

Product developers

Reuse rules and traceable outcomes in their own applications.

Needs to validate with their users

Method

From question to evidence file.

One approach to know what was read, how and with which evidence.

  1. Frame the question

    Define the scope, period and expected outcome.

  2. Set the rule

    Agree on the threshold, sources and quality criteria.

  3. Preserve the evidence

    Archive the data used and make the calculation reproducible.

  4. Explain the outcome

    Provide a file that can be challenged. If evidence is missing, leave it unresolved.

The journey of a question

  1. Question

    A place, a period, an expected outcome.

  2. Source

    An official publication, readable without an account.

  3. Rule

    Variable, unit, threshold and reference, written before the observation.

  4. Freeze

    On the set date, the published file is archived with its fingerprint.

  5. Resolution

    Yes, no, or unresolved when the evidence is missing.

  6. Challenge

    The file stays open to examination.

A threshold, a freeze date

Threshold Freeze Published value After the freeze: ignored
The published value is read at the freeze. A later revision by the producer does not rewrite the outcome. Schematic diagram, with no real data.

Geospatial

Every question has a place.

A station, a reservoir, an ocean region: the measurement is located, and that place is shown as it is defined.

A marker, not a border

A point marks a published station; an extent is an indicative window. A country outline helps to read the map; it bounds no measurement.

Open base maps

Plans, aerial photographs and satellite mosaics come from open sources, credited with their licence.

An image is not evidence

A location plan shows where the measurement is made, not its value. The date of the background is not the date of the question.

Schematic diagram: the markers are not real positions.

Prediction markets

A market is only worth its resolution.

A prediction market gathers opinions on a question whose outcome will be known. That outcome still has to be measurable, dated and open to examination by everyone.

What GeoOracle brings

The question, the rule, the source and the archived evidence: enough to decide without an opaque arbiter.

What GeoOracle does not do

No prices, no orders, no wallet. Trials use play points.

Where we stand

No market is open. Any trial stays a simulation in play points.

First use cases

Four fields to learn from.

Pilots studied through historical archives. Their purpose: test the rules and their limits.

River flow

Check a threshold at a station, taking data quality into account.

Agricultural rainfall

Calculate a rainfall index over a defined period, without inferring crop loss.

Wheat yield

Compare an official national statistic with an explicit threshold.

NGO documents

Check for specific documents, without treating their presence as proof of impact.

Strategy

Prove the value. Then open the infrastructure.

  1. Technical reliability

    Reproduce results, handle exceptions and know when to withhold a conclusion.

  2. Practical value

    Measure time saved and errors avoided against existing methods.

  3. Willingness to pay

    Identify verification useful and frequent enough for a first customer to fund it.

Over time, reusable evidence.

Our direction: a shared format across applications and multiple verification operators. Prediction markets are a possible application of this infrastructure.

The proposed model

API, archiving and resolution monitoring. A business hypothesis to validate through the first use cases.

Principles

Better not to conclude than to conclude wrongly.

Six principles guide every question, every rule and every screen.

  1. Measurable, or set aside

    Without a public source that publishes the value, the question is classed as not measurable, with the reason.

  2. The rule before the result

    Threshold, unit and freeze date are written before the observation. A historical replay is stated as such.

  3. “Unresolved” is never “no”

    Missing, doubtful or late evidence settles nothing.

  4. An illustration is not evidence

    Images, plans and outlines locate; only the archive of the source resolves.

  5. Limits are part of the result

    Each record says what was read, what was not, and what may change.

  6. No real money

    Play points only, with no affiliation to the organisations cited. Value is proven first on use cases.

Where to go next

GeoOracle

Questions, rules, evidence.

GeoOracle · Independent project in development

Search the documentation

Type at least two characters.

↑ ↓ to move · Enter to open · Esc to close