Select a case to inspect its requirements.
● Private research13 OCT 2026
EVIDENCE, RESTORATION NEEDS AND FUNDINGRESEARCH WORKSPACE 05
Where should
restoration focus?
Inspect a place, identify what the evidence supports, scope an intervention, and see which actors and funding conditions are still missing. Gaia preserves the reasons behind each assessment.
Two public cases · Connected station readings · Human review
A CLAIM IN CONTEXT · SCHEMATIC
CASE CONTEXT2 public casesLake Erie–Maumee · Deschutes
RESEARCH MEMORYPersistent revisionsVEOR notes and scoping dossiers
PYTHON COREChecking connectionSynthetic ERR impact preview
WHAT YOU CAN DO TODAY
From a place to a reviewable plan.
THE LEARNING LOOP
Observe. Assess. Plan. Review. Monitor. Revise.
Gaia’s long-term role is to connect planetary observation with accountable restoration decisions. Current tools support case scoping and review requests. Current local measurement ingestion, authenticated reviewer roles and validated intervention forecasts are the next gates.
REGIONAL NEEDS · ACTORS · FUNDINGPUBLIC CONTEXT + USER SCENARIO
A place needs attention.
What would a plan require?
Choose a sourced case. Examine pressure, possible interventions and missing evidence. Optional numbers are your planning assumptions; they are not observed field measurements or an approved project budget.
READ THIS BEFORE CALCULATING
Sources, observations and scenarios are separate.
The case descriptions and linked agencies provide research context. Monitoring-station values are public point observations, not a whole-basin diagnosis. Your inputs below are assumptions for a hypothetical scenario; output is not a site quote, verified phosphorus reduction, investment return or funding approval.
How to interpret Gaia evidence, sources and calculators ↗Station monitoring
Public point measurements and preserved provenance; no catchment-wide diagnosis.
CONNECTED PUBLIC MEASUREMENTS
Maumee River · station observations
One public point station. Readings retain their observation times, source units and provisional status. They are not automatically used as planning inputs or converted into a seasonal phosphorus load.
Checking saved source snapshot.
Source provenance and limits
Captured source snapshots
Historical observation series
BOUNDED HISTORICAL TIME SERIES
Antwerp · 12 October 2026 UTC
One upstream point station, two parameters, 00:00–24:00 UTC with both boundaries. This fixed day is separate from the latest station snapshots and the Maumee seasonal policy target.
Checking saved daily series.
Select a time to inspect its exact source readings. Green: matched endpoints pass the input contract. Amber: input is missing or held. The fixed 15-minute grid is an application inspection rule.
Captured series versions
Provenance, method and limits
Shared scoping workspace
Scenario inputs stay together. Diagnosis, interventions and finance each have a focused result page.
Preserve a draft. Request review.
Checking saved dossier.
A review request is stored in this workspace. No message is sent to a reviewer. Reviewer assignment, approval, implementation and payments remain unavailable.
Ecological diagnosis
Investigate evidence limits, source provenance and the requirements for a scientifically defensible diagnosis.
Loading the selected research case…
Intervention intelligence
Explore candidate interventions and governance requirements without claiming verified effectiveness.
Loading the selected research case…
Financial intelligence
Understand user-supplied budgets, funding gaps and readiness; no investment return is established.
Loading the selected research case…
Source catalogue & data rights
OPEN-DATA INGESTION PATH
Every source keeps its identity.
Restoration registries, basin context and measurements have different access and evidence roles. Connected datasets, archived inputs and planned integrations are labelled separately.
SCOPE AND VALIDATION27 CAPABILITY GROUPS
What works.
What is still missing.
Repository code, local validation and live web behaviour are separate. Regional scoping is a partial decision-support path; it is not a validated intervention or investment recommendation.
Test counts may overlap. Historical reports are not counted as fresh test execution.
EPISTEMIC REVISION RECORDSYNTHETIC EXPERIMENT
Knowledge changes.
Its impact is traceable.
Explore a proposed M_CANOPY revision from version 1 to 2. The live Python preview and explicit browser demonstration use synthetic records. Neither activates a method or changes a claim.
M_CANOPY · v1 → v2
Records requiring review
Selected for reviewNot selectedDashed: inactive dependency
—
A preview is not approval.No method activation, claim transition or new verification. The impact set depends on the supplied dependency snapshot, purpose and state filters.
CLAIM · EVIDENCE · METHOD6 SYNTHETIC RECORDS
Open a claim.
Inspect its connections.
V01–V06 are partial VEOR examples for the ERR experiment. They contain no real field measurement, geometry or independent verification. Public cases are in Regional opportunities.
Checking record source.
Loading records.
PERSISTENT RESEARCH RECORD
Save a note. Keep its history.
Use synthetic research notes only. Do not enter personal information, community knowledge or credentials. Notes are not verifications or ERR approvals.
Checking persistent record.
Earlier revisions are not edited or deleted by this application. Content hashes and history links are checked; they are not signed attestations. Notes do not alter the live ERR calculation.
Records and measurements are different.Synthetic placeholders and empty fields do not establish a completed intervention, restoration success or a payment entitlement.
OBSERVATION AND CLAIM BOUNDARIESDESCHUTES ARCHIVE
What does the
evidence establish?
The reviewed Deschutes archive contains an agency activity polygon and a fixed-candidate sensitivity audit. Descriptive spectral-index changes do not establish a causal treatment effect.
Activity contextArchived agency record
CausalityNot established
Restoration successNot established
Payment basisNot established
ARCHIVED RESEARCH
Preserved evidence, with explicit limits.
Regional opportunities shows the reviewed polygon, agency metadata and English analysis summary. Raw pixels are not recalculated here. The original historical report remains available in its original language.
Original archived report (Turkish) ↗RECOVERED PYTHON RESEARCHSYNTHETIC REPLAY
Test the protocol.
Keep its limits visible.
Inspect the original Amazon intake and benchmark modules after their reviewed inputs were restored. These saved results come from a local Python replay. Selecting a result does not run a new server computation or create an approval.
Loading reviewed research replay.
A candidate project is not a verified parcel.
Source versions and reproduction
Correct synthetic execution is one gate.Authenticated actors, independent consent, actual Amazon treatment boundaries, validated ecological response models and full scientific stabilization remain separate requirements.