Product
The OS
A B0rd is a sign that stays in the room. The operating system inside it starts with time and place. It finds when it is and where it is, then the next relevant thing can live on the wall. That is the primitive. Clock, countdown, weather, notify, and whatever you schedule after that are apps on top of it.
Every model shares B0rd OS: boot, display, network, settings, and a control plane you can use from a phone or a workstation. Screen types differ by model. The OS is the common layer so apps and habits transfer.
Why an OS
Time, place, and apps have to belong to one thing that keeps running. Firmware flashes once and freezes a behavior. An operating system owns boot, display, time, networking, settings, and a place forapps. That app surface is still maturing. The direction is a platform you can compose, not a one-shot image.
In sync by design
B0rd treats synchronized time as an operating-system input. Matching units use the same UTC moment and timing contract to choose the same scene, transition, and animation phase independently. They need network time, but they do not need a hub, leader, pairing relationship, or device-to-device animation protocol.
When authoritative network time is unavailable, every B0rd remains usable on its own local clock without pretending it is synchronized.
Apps
On B0rd, what appears on the screen comes from apps: background motion (for example plasma) and base chrome (for example launch countdown). More kinds may arrive later.
You do not download or sideload an app onto the device. Apps shipbuilt into the OS image for that product, not as a runtime app store on the unit. The shared platform keeps the idle clock, boot splash, settings, and USB / setup-network control plane. Product apps such as plasma and launch countdown ship in the product build alongside that core.