The technology layer
What edge compute means in a building — and how Autotelic runs it
What edge compute is in a venue, a commercial space, or a home, and the real systems Autotelic runs today, including its own venue operating system.
live
Edge compute, in a building, means processing happens on hardware physically located at that building instead of solely in someone else's data center — a server rack in a closet, a small cluster running the venue's own software, a controller running lighting and climate logic on site. The practical benefit is that the building keeps working, and keeps its own data, even if the internet connection to anywhere else drops; the practical cost is that someone has to design, install, and maintain that hardware properly.
In a home, this usually looks like a smart-home controller and a structured-cabling backbone. In a commercial space, it's enterprise networking, building automation, and often a server rack for the business's own systems. In a venue, it can run the whole operation — displays, audio zones, cameras, and the software coordinating all of it — from hardware the venue owns rather than a stack of third-party subscriptions.
Autotelic designs and installs that hardware layer directly: AI server clusters, server racks, enterprise networking, fiber backbone, building automation, and digital signage, among other technology trades, sized to the building.
The clearest example is Autotelic's own venue, BARna, which runs on a venue operating system Autotelic built: a staff app behind the venue's own network bridge, a message broker coordinating rooms, and room-level agents handling playout, TVs, projectors, and audio guarding. A power-recovery orchestrator checks the system daily, boots recovering hardware quickly, keeps an hourly state snapshot, and only sends a message to the owner when something looks worse than the last check — quiet by design when everything is fine. Camera-vision features some venues use for table tracking or crowd analysis are staff-only today and unverified as running in production, so they aren't claimed or drawn here.
Edge compute shows up differently by project type — fully, in a venue; at commercial scale in a commercial tenant finish or a new build; and in smaller moons for a home remodel or an ADU — but the same design-install approach applies across all five.
What it does
- Autotelic designs and installs AI server clusters, server racks, enterprise networking, fiber backbone, building automation, and digital signage.
- BARna, Autotelic's own venue, runs on a venue operating system Autotelic built and maintains.
- A staff app behind the venue's own network bridge and a message broker coordinate room-level agents for playout, TVs, projectors, and audio.
- A power-recovery orchestrator checks the system daily, boots recovering hardware quickly, and keeps an hourly state snapshot.
- It only messages the owner when a check looks worse than the last one — silent by design otherwise.
- Camera-vision features some venues use are staff-only and unverified as running in production, so they are not claimed here.
What it sees
{
"context": "After the 2026-08-18 venue-wide power loss left the headend and about 27 playout mini-PCs dark for 32 hours, the recovery was automated: every boot and every morning the orchestrator wakes the fleet, checks audio, powers the receivers, runs the fleet doctor, and texts the owner only when the picture is worse than the last report.",
"steps": [
{
"step": 1,
"label": "Trigger",
"detail": "Daily run at 04:45 (also on every headend boot, two minutes after startup); 45-minute cap."
},
{
"step": 2,
"label": "Wake the fleet",
"detail": "Magic packets from the headend to every playout and TV agent: 25 of 25 agents online within about 5 seconds on the 2026-09-05 run (on the first live run the night before, the headend's own wake packets brought back one basement screen that had been off)."
},
{
"step": 3,
"label": "Audio",
"detail": "The house audio interface is resolved by friendly name, not by a hardware id that changes after a power event; status: decoding."
},
{
"step": 4,
"label": "Receivers",
"detail": "DirecTV receivers powered: 8 of 8 on."
},
{
"step": 5,
"label": "Restore sources",
"detail": "Skipped by design on daily runs; after a boot, only screens whose agent has heartbeated and whose state differs are re-commanded. Screens a human set to another source are never touched."
},
{
"step": 6,
"label": "Fleet doctor",
"detail": "Health check across the room stack: failures went from 5 to 4 (one projector agent had not been running after its PC was powered on; started by hand later that morning)."
},
{
"step": 7,
"label": "Report and text",
"detail": "Report retained for the staff app's Ready tab. Owner text skipped: the rule is worse-only for routine runs (a newly missing agent or a higher doctor failure count); boots and failed steps always text."
}
],
"doesNotDo": "Sonos regroup, DirecTV retune, TV input fixes, agent restarts, headend reboot, and any volume or mixer write are deliberately outside v1.",
"openItems": "A rehearsed headend reboot in a quiet window; three basement screens off the network on the panel side; the projector agent's autostart."
}What it replaced
Nothing here replaced an old phase.
Proof
- ADUliveSmall moons only — structured cabling and EV charging, sized for an ADU.
- Home remodelliveSmart-home, structured cabling, and energy moons sized for a house.
- New buildliveEnterprise networking, structured cabling, and whole-home automation designed in from the start.
- CommercialliveEnterprise networking, building automation, and A/V sized for a tenant space.
- VenueliveThe full BARna venue OS: staff app, message broker, room agents, and the power-recovery orchestrator.
The system layer
The system behind edge compute: the hardware and software Autotelic runs inside a building, including its own venue operating system.
Topology
- Staff app (behind the venue bridge)
- Message broker
- Room agents (playout, TV, projector, audio guard)
- Power-recovery orchestrator
- Fleet doctor + hourly snapshot
- Karaoke rooms
- Enterprise networking
- Structured cabling
- Building automation
- Staff app (behind the venue bridge) → Message broker
- Message broker → Room agents (playout, TV, projector, audio guard)
- Message broker → Power-recovery orchestrator
- Power-recovery orchestrator → Fleet doctor + hourly snapshot
- Room agents (playout, TV, projector, audio guard) → Karaoke rooms
- Enterprise networking → Structured cabling
- Structured cabling → Building automation
The one-day clock
- 04:45 — BARna power recovery
- every 2 hours — Build-desk PR pulse
- every 5 minutes — Fleet watch
One replay
{
"context": "After the 2026-08-18 venue-wide power loss left the headend and about 27 playout mini-PCs dark for 32 hours, the recovery was automated: every boot and every morning the orchestrator wakes the fleet, checks audio, powers the receivers, runs the fleet doctor, and texts the owner only when the picture is worse than the last report.",
"steps": [
{
"step": 1,
"label": "Trigger",
"detail": "Daily run at 04:45 (also on every headend boot, two minutes after startup); 45-minute cap."
},
{
"step": 2,
"label": "Wake the fleet",
"detail": "Magic packets from the headend to every playout and TV agent: 25 of 25 agents online within about 5 seconds on the 2026-09-05 run (on the first live run the night before, the headend's own wake packets brought back one basement screen that had been off)."
},
{
"step": 3,
"label": "Audio",
"detail": "The house audio interface is resolved by friendly name, not by a hardware id that changes after a power event; status: decoding."
},
{
"step": 4,
"label": "Receivers",
"detail": "DirecTV receivers powered: 8 of 8 on."
},
{
"step": 5,
"label": "Restore sources",
"detail": "Skipped by design on daily runs; after a boot, only screens whose agent has heartbeated and whose state differs are re-commanded. Screens a human set to another source are never touched."
},
{
"step": 6,
"label": "Fleet doctor",
"detail": "Health check across the room stack: failures went from 5 to 4 (one projector agent had not been running after its PC was powered on; started by hand later that morning)."
},
{
"step": 7,
"label": "Report and text",
"detail": "Report retained for the staff app's Ready tab. Owner text skipped: the rule is worse-only for routine runs (a newly missing agent or a higher doctor failure count); boots and failed steps always text."
}
],
"doesNotDo": "Sonos regroup, DirecTV retune, TV input fixes, agent restarts, headend reboot, and any volume or mixer write are deliberately outside v1.",
"openItems": "A rehearsed headend reboot in a quiet window; three basement screens off the network on the panel side; the projector agent's autostart."
}Questions
What is edge compute, in plain terms?
Processing that happens on hardware physically at the building — a server rack, a small cluster, a controller — instead of solely somewhere else on the internet.
Does every project get edge compute?
Every project type can use some form of it; how much varies — a full venue operating system for a venue, enterprise-scale systems for commercial or new construction, and smaller moons like structured cabling for a home remodel or an ADU.
What happens if the venue’s system loses power?
A power-recovery orchestrator checks it daily, brings recovering hardware back up quickly, and only messages the owner when something looks worse than the last check.
Are camera-based features like crowd or table tracking running at BARna?
Not as a claim made here — those features are staff-only where they exist and unverified as running in production, so they are left off this page.