Docs · Start here
15-minute quickstart
Power a WB-1, mint a token, read five events, hot-reload a rule, and add a second zone.
Read more →
Docs · v1
Documentation
Day-one WB-1 setup, the complete Rule DSL reference, API overview, and topology patterns — written for the person holding the terminal.
Start with the 15-minute quickstart if a WB-1 is on your desk. Keep the Rule DSL reference open when the first useful rule becomes the fifth. The API overview covers REST and WebSocket schemas; the topology guide covers node placement and relay patterns.
Choose a path
| If you need to… | Start here | Time |
|---|---|---|
| power a unit and prove the event path | Quickstart | 15 min |
| write, review, or debug a rule | Rule DSL reference | reference |
| integrate an existing control plane | REST + WebSocket API | 20 min |
| place more than one node | Topology guide | 10 min |
| understand conflict order and timing | Bobulation Engine | 12 min |
Working conventions
The examples use http://bobulator.local, a token stored in WB_TOKEN, and
fictional device IDs. Replace those values; leave the command shape alone.
Everything shown runs against the same v1 surface used by the built-in
dashboard. There is no private dashboard API to discover later.
Version contract
The examples target API v1 and the stable firmware channel. Fields may be added to v1 responses; existing fields do not change meaning. Rule validation is fail-closed: an unknown operator or action rejects the candidate revision before the active rule set moves.
Every mutating request returns a revision ID. Keep it — it is the join between your deployment log and the WB-1’s hash-chained audit record.