From the project
Why parcel-first.
A short explanation of why the project keeps parcel-linked data private by default, limits claims, and treats shared intelligence as optional.
The short version
Regional forecasts and app notifications are useful, but they do not show parcel-level conditions. OESIS is open because this problem needs clear ownership, explicit uncertainty, and infrastructure that still works under partial adoption.
What this means
Neighbors need tools that do not expose the home by default. Builders need contracts they can implement clearly. Partners need a roadmap that distinguishes current scope from future phases.
The current scope is intentionally narrow — one parcel, real sensors, trust-scored outputs — and widens through pilots.
Why this approach
Regional maps and alerts often miss parcel-level conditions. Parcel-first framing keeps the focus on what can be observed or inferred for a specific site, with clear limits on confidence and data use.
It also means the system should be able to say:
- what the regional baseline suggested
- what parcel metadata implied before fresh readings arrived
- whether local conditions diverged from that baseline
- what changed once parcel evidence was fused in
That is the core value proposition. The goal is not to replace public data. It is to show when public data alone is not enough for a specific parcel.
The governance and open release pages define the specific policies, release boundaries, and technical materials behind that approach.