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—scope, governance links, and how current work relates to longer-term direction.
Governance and privacy summarizes ownership, sharing, and claims boundaries.
Architecture
The system family includes field nodes, software services, and shared-intelligence layers. This page distinguishes what is closest to field deployment from what is still staged or in R&D.
Implementers
Run one slice end to end—bench-air-class hardware through published software contracts—before branching to other modules.
Start from the released indoor / sheltered air node on the hub.
Ingest, inference, and parcel platform contracts linked from the hub.
Public-safe architecture flow before you open implementation-heavy repos.
Honest status table—opens the public repo in a new tab.
Builds
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.

Bench Air Node: proven reference build for repeatable indoor parcel evidence through the ingest-to-parcel-view stack.
Mast-lite outdoor node: sheltered outdoor sensing for weather and air at the parcel edge, bound with bench-air through the node registry.
Flood Node: optional low-point runoff evidence with full runtime lane, acceptance tests, and dedicated normalize/ingest modules.
Richer weather and particulate masts and privacy-minded thermal pods remain important but are not presented as equally mature in the current release.
Concepts
A richer outdoor mast combining weather and particulate context at parcel edge—successor path beyond mast-lite for full air + weather storytelling.
Ingest + inference + parcel platform as the coherent ‘engine’ that turns evidence into parcel state and dwelling-facing guidance.
Policy-gated shared map and future neighborhood layers—downstream of parcel ownership, optional by design.
Released hardware
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.
Indoor or sheltered air reference and the quickest way to get real readings through the full stack.
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
Sheltered outdoor reference for weather and air at the edge of the parcel.
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
Optional low-point runoff evidence where parcel context makes it operationally relevant.
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
Research-gated derived thermal scene metrics without raw imagery persistence.
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 pieces cover the parcel app, ingestion, inference, and optional neighborhood map outputs—each documented for implementers.
The dwelling-facing app and API surface for parcel status, evidence, and freshness.
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
Validates device packets and external feeds, then normalizes them into canonical observations.
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
Combines observations and context into parcel-state outputs with explicit uncertainty.
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
Optional coarse neighborhood outputs built from policy-gated shared signals.
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
Architecture indexes, contracts, and integrated BOMs live on the open release hub—this page summarizes the modular family for a technical audience without replacing the hub.