SNAPSHOT 2026-05-28·BUILD 0c187d0b·ENV public-demo·CC-BY 4.0·v0.1.0

doriiOS Public Launch And OBIS Integration

doriiOS should enter the aquatic-science community as a read-only, provenance-first research cockpit. The first public version is a demo, not a raw-data service and not an official OBIS product.

Public Demo Contract

  • Use DORIIOS_DEPLOYMENT_PROFILE=public-demo for web hosting.
  • Read app-ready data from src/data/public-demo-lake unless DORIIOS_PUBLIC_DATA_ROOT points at a published snapshot.
  • Keep the raw SSD lake private.
  • Force fixture-backed agents in public mode.
  • Block runtime vault writes in public mode.
  • Never set GBIF, OpenRouter, or OpenAI secrets for the public demo unless a private backend is added later.

Scientist-Facing Demos

  1. Find Species Coverage Gaps: open the map, filter a taxon, inspect missing images, missing depth, and source-citation gaps.
  2. Inspect Suspicious Records: open a map cell, compare records, datasets, year ranges, depth coverage, and provenance.
  3. Freshwater Crossover Dossier: open the freshwater run and show how GBIF samples, NWIS/WQP plans, and source governance fit together.

OBIS Contribution Path

  • Watch iobis/manual, iobis/obis-qc, iobis/obis-network-datasets, iobis/speciesgrids, iobis/pyobis, iobis/robis, iobis/obis-products-catalog, and iobis/obis-website.
  • Start with small reproducible docs/QC contributions.
  • Open GitHub issues only when doriiOS can show evidence, repro URLs, affected datasets or taxa, and a suggested upstream target.
  • Consider iobis/obis-products-catalog only after the public demo is stable and scientist feedback confirms value.

Outreach Rule

Ask for feedback, not adoption. The first ask is a 15-minute review of one workflow: “Does this help you trust the data, spot gaps, or prepare a cleaner OBIS contribution?”