Skip to main content

Pulse

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.

Customer impact desk

Support

Operational customer impact: who is affected, who is waiting, and what needs a hand now. Not the canonical support database.

Customer impact

7 active issues, 1 customer-impacting or critical, 4 waiting on an owner decision. Pulse can explain support impact but cannot reply to a customer, close a ticket or clear a hold.

Active issues

7

Open cases with any operational impact.

Urgent

1

Customer-impacting or critical.

Technical

3

Defect, outage, data, configuration or security.

Waiting on customer

UNKNOWN

Requires a support desk feed. Not connected.

Owner action 4 case(s) cannot progress until you decide.

Pulse snapshot · cases · Stale · 2026-08-06 17:30 UTC · Likely — Operational impact derived from recorded case files, not from a support desk feed.

No customer-support provider feed is attached. Everything below is derived from recorded Pulse cases — ticket counts, customer replies and SLA clocks are NOT CONNECTED / UNKNOWN, never estimated.

NOT CONNECTEDSupport · no timestamp

Atlas / Tower return contracts

  • PARTIALatlas/api/public/support-snapshot

    Read-only Support/Pulse snapshot for Atlas /api/atlas/pulse and /api/atlas/support adapters.

    Consumer env: PULSE_SUPPORT_BASE_URL — Payload is code-ready on Pulse. Atlas LIVE-FEEDS-ATLAS-READ-001 wires live fetch when PULSE_SUPPORT_BASE_URL is set; honesty stays PARTIAL until Hub caller + durable store proven. No secrets in snapshot.

  • PARTIALtower/support

    Tower product handoff into Pulse support watch desk (customer-impact observe).

    Consumer env: VITE_SUPPORT_URL — Tower already declares VITE_SUPPORT_URL. Point it at the Pulse origin + /support for watch. Canonical Support is OmniSupport Nexus — Pulse is not a second Support product. Missing URL stays setup-required — not Connected.

Snapshot: GET /api/public/support-snapshot

Outbound handoffs (Pulse → Atlas / Tower)

  • MISSINGOpen Atlas

    Setup required: set VITE_ATLAS_URL to an https URL.

    VITE_ATLAS_URL not set — Atlas return deep-link unavailable.

  • MISSINGOpen Tower

    Setup required: set VITE_TOWER_URL to an https URL.

    VITE_TOWER_URL not set — Tower product return deep-link unavailable. In-Pulse /control-tower still works.

In-Pulse Control Tower observe surface: /control-tower

Build / product repair hop

MISSINGApp Builder Hospital (build/product repair)GAPNOT CONNECTED

HMAC client posts to https://builder.kleinhubai.com/api/public/pulse/health-intake with header x-pulse-signature (sha256=). Shared secret PULSE_INTAKE_SIGNING_SECRET must be set on Pulse and App Builder. Pulse also needs APP_BUILDER_HOSPITAL_WORKSPACE_ID. Live hop remains NOT_CONNECTED until a signed intake is accepted. Pulse watch desks are not App Builder Hospital.

Mission Control / OmniSupport Nexus

MISSINGMission Control / OmniSupport NexusNOT CONNECTEDno GitHub repo

Canonical Support is OmniSupport Nexus (Lovable 530988ff). Emit safe ops signals to Pulse POST /api/public/hooks/omnisupport-signal (Bearer PULSE_SUPPORT_SERVICE_TOKEN). Pulse /support is watch/impact only — not a second ticket DB. Not CONNECTED until live emit proven.

  • Hub support evidence hop · PARTIAL · /api/public/hooks/hub-support-evidence
  • OmniSupport operational signal intake · PARTIAL · /api/public/hooks/omnisupport-signal
  • Tower support URL · PARTIAL · /support
  • OmniSupport Nexus (Lovable) · MISSING

HUB-RLS gate remains RED on KleinHub AI

High
No observed customer impactKleinHub AIWaiting on OwnerDIAGNOSED

No confirmed customer impact; risk is to data boundaries.

  1. Detect
  2. Triage
  3. Diagnose
  4. Guardian check
  5. Assign specialist
  6. Owner GO
  7. Repair
  8. Test
  9. Audit
  10. Guardian recheck
  11. Recovery watch
  12. Discharge

Pulse snapshot · HUB-RLS gate · Recent · 2026-08-06 17:30 UTC · Known

App Builder blocked on dirty worktree

High
No observed customer impactApp BuilderWaiting on GuardianDIAGNOSED

No customer impact observed in the current snapshot.

  1. Detect
  2. Triage
  3. Diagnose
  4. Guardian check
  5. Assign specialist
  6. Owner GO
  7. Repair
  8. Test
  9. Audit
  10. Guardian recheck
  11. Recovery watch
  12. Discharge

Pulse snapshot · app-builder · Recent · 2026-08-06 17:30 UTC · Known

Audit & Assurance docs ahead of synced state

Low
No observed customer impactAudit & AssuranceWaiting on UnknownDIAGNOSED

No customer impact observed in the current snapshot.

  1. Detect
  2. Triage
  3. Diagnose
  4. Guardian check
  5. Assign specialist
  6. Owner GO
  7. Repair
  8. Test
  9. Audit
  10. Guardian recheck
  11. Recovery watch
  12. Discharge

Pulse snapshot · audit-assurance · Recent · 2026-08-06 17:30 UTC · Known