Projects
Same truth pipeline. Different job.
RealWeather is the org layer: rules, provenance, sources, and public change logs.
CurrentWeather is the product layer: a dashboard that applies those rules to deliver usable weather.
Transparency surface
Executable product
Shared truth rules
Shared pipeline Fetch → validate → select → label (per field)
fetch obs + model candidates
→
validate freshness + bounds
→
select winner per field
→
label obs / model / derived
Org layer
RealWeather.org
Docs, receipts, and change log discipline.
Transparency
The documentation surface: methodology, data sources, failure modes, and what changed — with receipts/specs
when applicable. If we can’t explain it, we don’t pretend it’s “current.”
Outputs Rules, provenance definitions, and public change logs
Promise No hidden logic, no hand-wavy “trust us”
Measurement
Aggregate usage only. We use Cloudflare edge analytics (page views, referrers, coarse geography) for
reliability and operational health — not behavioral analytics, profiling, fingerprinting, or user-level IDs.
Product layer
CurrentWeather.info
The dashboard that executes the rules.
Executable truth
A high-signal weather dashboard. Hybrid obs/model truth, visible provenance indicators, and behavior that’s
designed to be auditable. (UI provenance exists today; exportable receipts are the next step.)
current_temp obs
wind model
dew_label derived
Next
What lands here over time: public roadmap, status page, API notes, and metric-level receipts/specs
(definition, provenance, selection rules, validations, freshness windows, and known failure modes).
This becomes the public spec surface as the product expands. Track changes → Last updated: December 2025