v0.1
Bench Air Node: proven reference build for repeatable indoor parcel evidence through the ingest-to-parcel-view stack.
New here? Start with the Program overview for an overview of the initiative, or Governance and privacy for ownership, sharing, and data boundaries.
Architecture
Systems
OESIS is made up of sensor nodes you can build, software that turns readings into a parcel view, and shared-intelligence layers for optional neighborhood context. This page shows what is closest to real sites right now, what is staged for later, and where each piece fits, while keeping packet-status boundaries explicit.
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
Architecture flow diagrams before you open implementation-heavy repos.
- v1.0 scope (program-specs)
Honest status table—opens the public repo in a new tab.
Builds
What is closest to real sites right now
Some modules are documented earlier than they are field-ready. Bench-air is the proven v0.1 reference, mast-lite is the v0.2 outdoor node, flood-node is v0.3, and richer weather/particulate masts and thermal remain staged. Publication packet status can still be partial or deferred for some lanes.
v0.2
Mast-lite outdoor node: sheltered outdoor sensing for weather and air at the parcel edge, bound with bench-air through the node registry.
v0.3
Flood Node: optional low-point runoff evidence with full runtime lane, acceptance tests, and dedicated normalize/ingest modules.
Staged / R&D
Richer weather and particulate masts and privacy-minded thermal pods remain important but are not presented as equally mature in the current release.
Concepts
Planned & cross-cutting
This section is the architecture coverage map: current modules, next-promotion surfaces, and later bridge layers are listed separately so "documented" is not confused with "fully shipped."
in specs
Weather + PM mast
A richer outdoor mast combining weather and particulate context at parcel edge—successor path beyond mast-lite for full air + weather storytelling. Hardware spec and build guide exist; ingest normalization is not yet implemented.
in specs
Parcel engine
Ingest + inference + parcel platform as the coherent ‘engine’ that turns evidence into parcel state and dwelling-facing guidance.
in specs
Shared neighborhood intelligence
Policy-gated shared map and future neighborhood layers—downstream of parcel ownership, optional by design.
in specs
Runtime module boundary
Canonical runtime modules are ingest, context, inference, parcel platform, and checks, with executable implementation in the sibling runtime repository.
planned
Indoor response + outage bridge
v1.5 bridge surfaces add indoor-response and outage evidence so the system can evaluate hazard -> house state -> action -> measured outcome loops.
in specs
Equipment-state + circuit monitor
CT clamp circuit monitoring for HVAC and sump confidence. Hardware spec exists; ingest normalization is not yet implemented. Full integration is a v1.5 capability target.
planned
Freeze-node module
Geography-gated freeze evidence remains a planned module for cold-climate parcels, not a universal default.
Released hardware
Hardware modules
Open hardware modules cover indoor air, sheltered outdoor reference, optional flood points, and a privacy-minded thermal option. Each has build and firmware docs for makers.
released
Bench Air Node
Indoor or sheltered air reference and the quickest way to get real readings through the full stack.
Technical detail and doc linksExpand
Produces the first repeatable indoor or sheltered parcel evidence and exercises the full ingest-to-parcel-view path.
Why it matters: It is the fastest hardware route from concept to trustworthy parcel evidence.
Relevant diagrams: System context, Recommended first integrated prototype
next
Mast-Lite Outdoor Node
Sheltered outdoor reference for weather and air at the edge of the parcel.
Technical detail and doc linksExpand
Adds sheltered outdoor parcel context without waiting for the richer mast build.
Why it matters: It is the simplest outdoor step that turns a single-structure slice into a fuller parcel kit.
Relevant diagrams: Recommended first integrated prototype, Parcel view surface
next
Flood Node
Optional low-point runoff evidence where parcel context makes it operationally relevant.
Technical detail and doc linksExpand
Measures low-point runoff evidence while staying explicit that one point is not the whole parcel story.
Why it matters: It adds flood-specific evidence without pretending a single sensor point is parcel-wide truth.
Relevant diagrams: Recommended first integrated prototype, Data-rights and visibility boundary
planned
Weather + PM Mast
Second-wave outdoor mast for richer particulate and weather context at parcel edge.
Technical detail and doc linksExpand
Extends outdoor evidence beyond mast-lite by adding a weather-plus-particulate hardware path with dedicated build and firmware docs.
Why it matters: It is the upgrade path when teams need stronger outdoor PM and weather evidence than the first sheltered-outdoor step.
Relevant diagrams: System context, Parcel view surface
planned
Circuit Monitor
v1.5 bridge hardware for read-side equipment-state evidence from CT-clamp current signals.
Technical detail and doc linksExpand
Captures HVAC and sump-adjacent equipment state as an explicit evidence stream, including cycle and confidence metadata.
Why it matters: It supports the hazard-to-response bridge by adding measured equipment behavior without implying full controls automation.
Relevant diagrams: System context, Data-rights and visibility boundary
planned
Thermal Pod
Research-gated derived thermal scene metrics without raw imagery persistence.
Technical detail and doc linksExpand
Provides area-level thermal context through privacy-safe derived metrics rather than stored frames.
Why it matters: It opens a path to scene sensing while preserving the project’s privacy posture.
Relevant diagrams: Parcel view surface, Data-rights and visibility boundary
Released software
Software services
Software pieces cover the parcel app, ingestion, inference, and optional neighborhood map outputs—each documented for implementers.
next
Parcel Platform
The dwelling-facing app and API surface for parcel status, evidence, and freshness.
Technical detail and doc linksExpand
Turns parcel-state outputs and evidence summaries into a usable parcel view without hiding uncertainty.
Why it matters: It is the main product surface where parcel awareness becomes usable rather than buried inside pipeline internals.
Relevant diagrams: System context, Parcel view surface
released
Ingest Service
Validates device packets and external feeds, then normalizes them into canonical observations.
Technical detail and doc linksExpand
Creates the evidence boundary that turns raw packets into the parcel-first information model.
Why it matters: It is the place where raw measurements become consistent, inspectable evidence for the rest of the system.
Relevant diagrams: System context, Recommended first integrated prototype
released
Inference Engine
Combines observations and context into parcel-state outputs with explicit uncertainty.
Technical detail and doc linksExpand
Turns normalized evidence into parcel-state guidance while keeping reasons, freshness, and confidence visible.
Why it matters: It is where parcel evidence becomes parcel-state guidance without pretending sparse evidence is certainty.
Relevant diagrams: System context, Data-rights and visibility boundary
next
Shared Map
Optional coarse neighborhood outputs built from policy-gated shared signals.
Technical detail and doc linksExpand
Creates a neighborhood condition layer that remains downstream of parcel ownership and sharing controls.
Why it matters: It is the part of the stack where network effects become visible without exposing raw parcel data.
Relevant diagrams: System context, Data-rights and visibility boundary
Implementers
Full spec collections & build guides
Architecture indexes, contracts, and integrated BOMs live on the open release hub. Runtime module implementation lives in the sibling runtime repository; this page summarizes the modular family for a technical audience without replacing canonical status docs.
For packet-level status (in, partial, deferred), verify against the program-specs v1.0 scope table.