Intent, Deployments, and Revisions
How WaSense represents building scope, working state, drafts, and published local intent.
Deployment scope #
An IoT deployment is WaSense's local container for one supported root location. The current page is scoped to a building-equivalent node; its managed rows may cover multiple floors below that node.
Working, draft, and current state #
| State | Meaning |
|---|---|
| Working state | The rows currently shown and edited. It uses an open draft when present, otherwise the current published revision. |
| Draft revision | Unpublished changes that can be reviewed, compared, edited, or cleared. |
| Current revision | The published local intent used as the approved WaSense baseline and by monitoring for exact per-device comparison. |
Revision lifecycle #
Creating or changing managed rows opens a draft. Publishing promotes that draft to the current revision and preserves the previous revision history. A failed external remediation does not silently change the meaning of the approved local revision; external operation results remain separately auditable.
Monitoring precedence #
For each observed AP, monitoring first looks for a row in the current published revision. That row is exact and includes BLE mode, gateway mode, beacon profile, UUID, major, minor, power, advertising power, interval, and the snapshotted IOx version. If no published row exists, monitoring falls back to the live building intent profile overlaid on the tenant default.
Draft rows never affect monitoring. Later profile edits also do not rewrite already published AP intent. One AP may belong to only one active published deployment.