Pulse is communications/watch (scan, classify, route, watch).
App Builder owns Hospital. Canonical Support is Mission Control / OmniSupport Nexus — Hub and Tower already have support surfaces. Pulse does not invent a second Support product and does not claim CONNECTED without an observed exchange.
Scan / classify / route / watch · Command
Watch Command
Whole-system scan, classify, route and watch: products, incidents, assignments, approvals, and recovery.
Reason: 2 protected actions held by Guardian.
Active cases
7
Urgent
2
Critical or high
Desk theme
Communications watch board
Owner action
Decide 6 Guardian gate(s) waiting on you.
Worker action
No work order is routed to this ward.
Pulse snapshot · portfolio-snapshot · Stale · 2026-08-06 17:30 UTC — 7 patient(s) have no live feed; those rows read Not connected on purpose.
Guardian Blocked2 protected actions held by Guardian.Little Buddy — what happens in Command?
This is the Pulse watch board. It shows how everything is doing at a glance. Repair belongs to App Builder Hospital.
This is the front desk. It shows how the whole family of products is doing right now.
Most numbers come from a saved snapshot, not a live feed, so they can be behind.
Two things wait on you: the hub security gate and the decision to publish this rebuild.
6 protected actions are waiting on your decision.
7 cases are open across watch desks.
Mail, support, Tower and run feeds are not attached, so parts of the watch board read Unknown on purpose.
Watched products
12
7 without a feed
Open cases
7
0 critical · 2 high · 4 medium
Waiting on owner
6
2 Guardian gates blocked
Proven work starts
0/5
No run feed attached, so no start can be proven
Emergency Watch
Critical outages, severe failures and urgent customer impact are received and worked here first.
Known · 7 sections
Triage Department
New alerts are classified, given a severity and an owner, then routed to the right desk.
Known · 8 sections
Diagnostics Laboratory
Evidence is gathered and root cause is established here. Guesses stay labelled as guesses.
Known · 9 sections
Security Watch
Protected areas are held here until Guardian and the owner clear them. Pulse never executes a protected action.
Known · 10 sections
Deployment Watch
Release readiness is shown here. Pulse can display readiness but never deploys or publishes.
Known · 10 sections
Support Watch
Customer-facing impact is watched here. Canonical Support is OmniSupport Nexus (Hub/Tower already have surfaces). Pulse does not own Support.
Disconnected · 9 sections
Recovery Watch
Repaired products are observed here. No case is discharged without proof.
Known · 9 sections
Watched products
Every real business, product, shared system and piece of infrastructure has a watch card with its own source.
Known · 5 sections
Route / Dispatch
Work orders are written and routed to specialists through BuildCommand. Assigned work is not started work.
Known · 10 sections
HUB-RLS gate remains RED in the latest snapshot; production and specialist branch alignment confirmed but the security gate is unresolved.
Pulse snapshot · kleinhub-main · Recent · 2026-08-06 17:30 UTC · Known
Recovery work reported closed and SHA-aligned at the last republish check; latest known status is WARNING in the snapshot, so it stays under observation rather than being called healthy.
Pulse snapshot · newsstand · Recent · 2026-08-06 17:30 UTC · Known
Snapshot reports BLOCKED with a dirty worktree and WIP triage outstanding.
Pulse snapshot · app-builder · Recent · 2026-08-06 17:30 UTC · Known
Snapshot reports WARNING with a sync-pending / ahead-docs state.
Pulse snapshot · audit-assurance · Recent · 2026-08-06 17:30 UTC · Known
Communications/watch rebuild in progress; GitHub is the only authoritative live feed, every other feed is explicitly unconnected.
Pulse snapshot · all-builds · Recent · 2026-08-06 17:30 UTC · Known
No Tower feed is attached to Pulse.
Tower · Not connected · no timestamp · Unknown — Tower feed not attached.
No repository, project or feed registered with Pulse.
Pulse snapshot · Not connected · no timestamp · Unknown — Patient registered by name only; no feed.
Marketplace has not been registered; Pulse holds a placeholder room only.
Pulse snapshot · Not connected · no timestamp · Unknown — Not registered.
No mail provider feed is attached; delivery, bounce and queue health are unknown.
Mail Office · Not connected · no timestamp · Unknown — Provider feed not attached.
No BuildCommand feed is attached; assignments shown are snapshot-derived only.
BuildCommand · Not connected · no timestamp · Unknown — Feed not attached.
Protected actions are held open and waiting on an owner decision; Pulse can display gates but can never clear one.
Guardian · Not connected · no timestamp · Unknown — No Guardian feed attached; gates are snapshot-held.
No support feed is attached, so ticket volume and response health are unknown.
Support · Not connected · no timestamp · Unknown — Support feed not attached.
7 open cases across watch desks. Nothing here can be published, deployed, migrated or cleared from Pulse.
Read-only view. Pulse never publishes, deploys, migrates or clears a Guardian gate.