Every command has one explicit destination.
Clients do not invent broker routes or Controller identities. The serving application maps authorized intent to a bounded destination.
Public documentation
Architecture before incantation.
Start with system boundaries, operating state, safety rules, and deployment assumptions. Copy-pasting commands without understanding those is how infrastructure develops personality disorders.
$ frame docs list
controller edge identity and local policy
analytics state, rules, alerts, schedules
integration typed messages and credentials
demo one bounded physical command
$
Read by boundary
Find the layer you are responsible for.
These pages describe public concepts and the reference demo. Customer deployments have their own versioned schemas, credentials, equipment maps, and operating procedures.
Operators and integrators
Cellular Controller
Connectivity, telemetry, relays, field deployment, and safe command handling.
Operators and analystsAnalytics Engine
Dashboards, schedules, alerts, customer modules, and decision workflows.
Developers and platform teamsIntegrations and Messaging
How Controllers, the Master Controller, and customer systems exchange typed events.
Visitors and technical evaluatorsPublic LED Demo
The deliberately constrained browser-to-RabbitMQ-to-Raspberry-Pi demonstration.
Documented invariants
Rules that survive implementation details.
Libraries, brokers, modems, and frameworks change. The safety and operational boundaries below should not quietly mutate with them.
Control requests expire.
A command that was safe fifteen seconds ago may be nonsense after a reconnect. Expiry and replay state are part of the contract.
Transport acknowledgement is not actuation.
The operator needs command lifecycle and, where practical, physical evidence or measured state after execution.