Audience path
Parcel operators and neighbors
Short reads first
Start with the problem gap and parcel-first framing, then governance for ownership, sharing, and claim limits.
Open source project
Open source environmental sensing, grounded where you are.
Climate hazards are getting more local. The infrastructure to sense, interpret, and act on them at the site level — with trust, privacy, and honest uncertainty — is what we're building.
OESIS fuses indoor and outdoor sensor readings, site context, public hazard feeds, and nearby shared evidence into one trust-scored view — with confidence levels and reasons shown for every output.
Every output shows what was observed, what was inferred, and how strong the evidence is — so you can check the reasoning, not just trust a score.
Smoke, heat, floodTrust-scored evidenceYour data stays yoursAdvisory, not alerts
Who this is for
Find your path
Start where you are; depth stays one click away.
Audience path
Builders and integrators
Plain language, then specs
Evidence layers, modes, and advisory outputs in plain language—then hardware, software, and schemas on the open release hub.
Audience path
Partners and pilots
Align expectations, then engage
Follow the roadmap, pilot scope, and how to plug into deployment—after the short Why it matters / How it works spine so expectations stay aligned.
Why this matters long term
The gap between regional data and your site is growing
Climate-related hazards are becoming more frequent and more localized. Public alerts tell you what is happening regionally — but not what it means for your specific site, your indoor air, or your next decision as an occupant.
Prove the pipeline works end to end: sensor readings through inference to a parcel view with trust scores and honest uncertainty.
Test whether nearby parcels can share coarse signals without exposing private data — making each parcel smarter without central surveillance.
Communities understand shared risk collectively, with governance that keeps each occupant in control of their own data.
Parcel-level evidence complements emergency services, insurers, and utilities — better ground truth for institutions, better context for occupants.
Each step only works if the previous one earns trust through field use. That is why the current scope is deliberately narrow.
Active development
Version arc
v0.1–0.5 is where the work is happening right now. Each version is a promoted runtime lane with its own acceptance tests — not a marketing label.
- Reference pipeline through governance enforcementFive active runtime lanes: reference pipeline, indoor+outdoor sensing, flood coverage, trust scoring, and governance enforcement.Active development
Bench-air + mast-lite + flood-node, node registry, trust gates, consent/revocation/retention/export enforcement.
- Measurement-to-intervention bridgeAdds the minimum bridge from hazard sensing to house-state, action, and measured outcome reasoning.Next build target
Introduces response and verification support surfaces without implying full automation or mature controls compatibility.
- Block intelligenceFirst sparse shared intelligence across nearby parcels.Future direction
Introduces block-scale derived intelligence without abandoning parcel ownership rules or the parcel-first operating model.
- Neighborhood networkNeighborhood coordination becomes a first-class product layer.Future direction
Extends from block-scale inference to broader neighborhood coordination, richer shared signals, and clearer network behavior.
- City federationFederated local systems connect at city scale.Long-range direction
Connects larger areas without collapsing local control, parcel ownership, or neighborhood-level governance.
Implementers
First build path
Run one slice end to end—bench-air-class hardware through published software contracts—before branching to other modules.
- Bench Air (hardware hub)
Start from the released indoor / sheltered air node on the hub.
- Software specs
Ingest, inference, and parcel platform contracts linked from the hub.
- Diagrams
Public-safe architecture flow before you open implementation-heavy repos.
- v1.0 scope (program-specs)
Honest status table—opens the public repo in a new tab.
From the maintainer
What I am running against v0.1–v0.5
This reflects the maintainer’s publishing and engineering focus—not a warranty that every pilot site, partner, or contributor matches the same checkout, hardware mix, or timeline.
Last updated April 2026
- Public site structure and copy kept aligned with the program-specs open release packet and phased roadmap.
- Engineering attention on the bench-air-first reference path and parcel-facing read contracts described on the open release hub.
- Pilot geography and field milestones are partner-dependent; the site does not claim nationwide or production deployment.
Implementation horizon
Shipping now versus long-term direction
Active development spans v0.1 through v0.5 — from the reference pipeline through trust scoring and governance enforcement. Each version is a promoted runtime lane with its own acceptance tests. Later capability stages like v1.5 remain architecture-only.
This is a long-term effort built through pilots, documentation, and gradual field use.
v0.1–v0.5 active development
Five runtime lanes progressing from reference pipeline (v0.1) through indoor+outdoor sensing (v0.2), flood-capable runtime (v0.3), trust scoring and node registry (v0.4), to governance enforcement (v0.5). Each lane has acceptance tests and a promotion bar.
What this scope covers
- v0.1: One parcel, one bench-air node, full pipeline from ingest to parcel view
- v0.2: Add mast-lite outdoor node for two-node parcel operation
- v0.3: Add flood-node for three-hazard coverage
- v0.4: Node registry, trust gates (freshness, confidence, cross-source disagreement)
- v0.5: Consent, revocation, retention cleanup, export bundles
- Three hazard tracks
- Trust-scored
- Governance enforced
- Pilot + partnerships in parallel
Each version is a promoted runtime lane, not a marketing label.
Long-term direction
Over time, the program aims to support predictive software for local climate-related conditions and hazards. It combines local observations, parcel context, public data, and optional neighborhood evidence in ways that remain useful under partial adoption.
What later phases add (direction, not a commitment)
- More neighborhood and multi-parcel evidence under opt-in sharing rules
- Clearer links from measurement to house state, interventions, and verification
- Operating models that support shared intelligence without giving up parcel operator control
- Outputs that complement official alerts, insurers, and utilities
- Multi-scale networks
- v1.5 intervention bridge
- Shared by choice
- Complements official systems
The parcel stays the anchor for decisions as scope expands.
System pillars
Three rules that hold across every release
Technical modules and releases change; these ideas stay fixed. Details live on Program and Governance and privacy.
- Parcel first — The product thinks about your whole site, not only a regional forecast.
- Private by default — Sensors and readings belong to the parcel operator unless you explicitly share.
- Shared by choice — Anything broader than your site is optional and controlled by policy you can see.
How we ship
Scope, labels, and where to verify
- Start here for project intent and current scope, then verify publication boundaries on Open release.
- v0.1–v0.5 are the active runtime lanes; formal version language and promotion criteria live on Program and Roadmap.
- Near-term work stays narrow on purpose: one parcel-first slice now, a fuller parcel kit next, broader capabilities later.
- Long-term value depends on pilots, trust, and field learning over time, not one launch moment.
Near term
Current pilot focus
The field pilot moves the program from reference docs to real sites in one defined local geography. It focuses on repeatable installs, structured feedback, and operational learning. Geography, goals, and partner paths are on the pilot page.
Latest progress
v0.1–v0.5 scope and site alignment
April 2026
The site now describes the active v0.1–v0.5 runtime lanes: reference pipeline, indoor+outdoor sensing, flood coverage, trust scoring, and governance enforcement. Next: pilot geography with partners and field milestones as they land. Project note.
Organize
Help shape the pilot
We are organizing community partners, pilot sites, builders, and funders. Pick a path on Get involved—or start with the Pilot page if you represent a site.