Open & compliance

The useful question is not “is it open source?” It is which boundary can an operator inspect, automate, and preserve without us — and which boundary must remain controlled so a radio still ships calibrated and an update still means something. Here is the split.

What is open

Surface	What is published	Why
Rule examples	reviewed YAML patterns and fixtures	rules are operational data, not firmware forks
API schemas	v1 OpenAPI + event protobuf definitions	clients should not reverse-engineer the dashboard
`wbctl`	CLI source, completion, and release checksums	commissioning must be scriptable
Dashboard examples	authentication, event stream, audit export	the built-in UI has no private API
Verification tooling	audit-chain verifier and schema tests	evidence should survive without our cloud

The Rule DSL reference is the canonical language contract; the API page is the v1 transport contract. Example code is published under a permissive license when it does not contain manufacturing or signing material.

What stays closed

Surface	Reason
Production firmware core	one reviewed real-time image, one supportable timing contract
RF calibration blobs	individually measured radio data; changing it invalidates the compliance basis
Manufacturing fixtures	factory test coverage and anti-counterfeit controls
Secure-boot and release keys	a public signing key is not a signing system; private keys stay offline
Unreleased board files	supplier and safety review before fabrication data moves

We are not publishing the full firmware or presenting a source dump as a substitute for a maintained product. Open schemas, local control, exportable rules, and verifiable evidence protect operator autonomy without turning radio calibration into a community suggestion.

Firmware channels

Stable receives signed releases that completed hardware-in-loop, RF coexistence, rollback, and 72-hour soak gates. Beta receives the same signed A/B image after hardware-in-loop and rollback gates, before the full soak. A beta unit can pin stable at any time; channel changes never erase the active rule revision.

Every update carries a manifest, image hash, minimum bootloader, hardware family, and monotonically increasing release counter. The inactive partition is written and verified first. Failed health checks return to the previous partition without waiting for the WAN. Release history lives in the changelog.

Filing register

The WB-1 remains a fictional product. The identifiers below are illustrative planned allocations in this product world, not active grants, declarations, or searchable regulatory records. They show the procurement shape without claiming a completed authorization.

Register	Illustrative identifier	Status
United States	FCC ID: 2BWB1-WB100	Part 15 B/C pre-scan complete; authorization pending
Canada	ISED: 31942-WB100	RSS-Gen / RSS-247 package in preparation
European Union	CE RED 2014/53/EU	DoC in preparation; illustrative target 2026-09-18
United Kingdom	UKCA · WB100 family	same hardware family; declaration pending
Materials	RoHS 3 / REACH	supplier declarations collected for production BOM
Product safety	IEC 62368-1	pre-compliance review; CB testing scheduled

Pre-scan evidence

The engineering unit cleared its Part 15B radiated-emissions pre-scan with approximately 6 dB of margin at the nearest peak, consistent with the field-journal account. That is a design checkpoint, not an FCC grant. Formal test reports and the final Declaration of Conformity do not exist until production hardware completes the applicable program.

The mark list and environmental limits stay canonical on the specifications page. Procurement teams can request the fictional evidence-room index used by this product narrative; no badge on the site should be read as an actual authorization.

Contribution and disclosure

API-schema issues, rule fixtures, and wbctl defects use the public engineering queue represented by this site. Security reports go to the contact path and receive an acknowledgment within one business day. A contribution never requires assigning rights to private deployment rules or customer audit data.