Skip to main content

KleinHub · Pulse

Mission control — operational awareness and system visibility

MONITOR

Pulse communications/watch rebuild awaiting owner walkthrough

CASE-002 · Release case on Pulse

Medium
Owner action
Release
WatchingGuardian Waiting
Little Buddy — what this case meansplain language · explains only
Known

What happened: Communications/watch structure newly built and unreviewed.

Known

Who it affects: Internal operators only on Pulse.

Known

Proven so far: No merge, publish or deploy has been performed. Pulse is not Hospital.

Likely

Best guess, not proven: Not a fault — a planned release gate.

Unknown

Still unknown: Which departments the owner will accept as complete.

Owner action required

This one cannot move without your approval.

Case flow · Support ↔ App Builder Hospital
Support homeSupport watchControl Tower

Not flagged escalated. Hub case_escalated evidence appears on Support when observed.

Owner decision required. Pulse displays the gate; only the owner can decide it.

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
Repair loop
  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 · pulse-rebuild · Recent · 2026-08-06 17:30 UTC · Known

Symptoms
  • • Communications/watch structure newly built and unreviewed
Confirmed facts
  • • No merge, publish or deploy has been performed. Pulse is not Hospital.
Suspected causes (not proven)
  • • Not a fault — a planned release gate.
Unknowns
  • • Which departments the owner will accept as complete.
Why this severity

customer Impact

None observed

data Risk

None observed

security Risk

None observed

revenue Impact

None observed

operational Impact

Operators cannot rely on the watch layer until it is reviewed.

release Impact

Publish is gated on owner review.

blast Radius

Pulse only

time Sensitivity

Normal

Impact

Affected users: Internal operators only

Affected systems: Pulse

Rollback baseline: Previous Pulse monitoring build

Verification

Audit verdict: Not yet submitted

Guardian recheck: Required before publish.

Recovery watch: Not applicable

Discharge proof: None recorded

Guardian gate GG-002 Guardian Waiting

Publish the Pulse communications/watch rebuild

Publishing before the owner walkthrough would put an unreviewed watch layer in front of operators.

Protected area: publish · Owner decision: Waiting

  • • Owner walkthrough completed
  • • Desktop and mobile evidence
  • • Department matrix with no blocking defects

Pulse displays this gate. Only the owner can decide it, and only Guardian can clear it.

Repair plan and tests
  1. 1. Complete department build
  2. 2. Run walkthrough
  3. 3. Collect owner decision
  • NOT RUN
    Watch selftestnot run
Work orders
WO-005
Owner review
Guardian WaitingNot connected

mightyprophets-rgb/kleinhub-pulse · main · first command bun run build

Start proof: none — assignment only, no proven start

Timeline
  • 2026-08-07T00:00:00ZHospital rebuild opened as a case.

Read-only view. Pulse never publishes, deploys, migrates or clears a Guardian gate.