Friday · 7:25 PM · one evening, frozen from the live deployment
The deployment running today is a single licensed hospitality site, so that is what this screen shows. The reading is the same in a stadium, a campus, or a multi-site estate; the questions change, the machinery does not. This is a live product, running today at a real venue on a Signals appliance. The numbers are real, taken
from that deployment and anonymized, then frozen at one moment, Friday 7:25 PM, so every card on this page reads from the same clock.
Integrations marked ROADMAP are deliberately forward-looking.
Everything tagged AUTO happened without a human;
SUGGESTED means the brain proposes and you tap yes.
Ask the operation · five questions, answered from the dataset behind this page
Five worked examples over this page's anonymized dataset. In a deployment you type your own question and the model answers it from your own database.
VITAL SIGNS · TONIGHT AS OF 7:25 PM
Sales tonight
$4,213
▲ 12% vs last Friday
Gross margin
$1,687 40%
▲ +2.1 pts · item costs from the register
Visitors
143
▲ 9% · counted by cameras, deduplicated; nobody identified
Spend / visitor
$29.46
▼ $1.10 · traffic up, ticket flat
Conversion
61%
walk-ins who bought · ▲ 4 pts
Labor vs traffic
4 on
right-staffed · next peak 8 PM
The rest of the brain
You are looking at the vital signs. The live floor, the inventory brain, the watchlist and the business case sit behind a work email. Enter one and the rest loads.
Signals by YYZdata · deployed in production at a live venue · scenario frozen at Friday 7:25 PM, anonymized from the live deployment · roadmap items marked · no video stored, no identity tracked by default · register & inventory read-only
YYZdata