Skip to main content

KleinHub · Pulse

Mission control — operational awareness and system visibility

MONITOR

App Builder blocked on dirty worktree

CASE-003 · Defect case on App Builder

High
Blocked
Defect
BlockedGuardian Blocked
Little Buddy — what this case meansplain language · explains only
Known

What happened: Worktree reported dirty.

Known

Who it affects: Internal builders on App Builder.

Known

Proven so far: Snapshot reports the App Builder lane as BLOCKED with a dirty worktree.

Likely

Best guess, not proven: Uncommitted work-in-progress left on the lane (suspected).

Unknown

Still unknown: Which files are dirty and whether the changes are wanted.

Known

A worker moves this next; you do not need to do anything.

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

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

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 · app-builder · Recent · 2026-08-06 17:30 UTC · Known

Symptoms
  • • Worktree reported dirty
  • • Validation not run
  • • Status BLOCKED
Confirmed facts
  • • Snapshot reports the App Builder lane as BLOCKED with a dirty worktree.
Suspected causes (not proven)
  • • Uncommitted work-in-progress left on the lane (suspected).
Unknowns
  • • Which files are dirty and whether the changes are wanted.
Why this severity

customer Impact

None observed

data Risk

None observed

security Risk

None observed

revenue Impact

None observed

operational Impact

Lane cannot validate or release while the tree is dirty.

release Impact

All App Builder releases blocked.

blast Radius

App Builder lane

time Sensitivity

High — blocking other work orders.

Impact

Affected users: Internal builders

Affected systems: App Builder lane

Rollback baseline: Last clean App Builder commit (unknown in snapshot)

Verification

Audit verdict: Not run since block

Guardian recheck: Required only if migrations are involved.

Recovery watch: Not started

Discharge proof: None recorded

Guardian gate GG-004 Guardian Blocked

Apply pending migrations on the App Builder project

Migrations against a dirty worktree can apply unreviewed schema changes.

Protected area: migrations · Owner decision: Waiting

  • • Clean worktree proof
  • • Migration list with reviewed SQL
  • • Backup / rollback baseline

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

Repair plan and tests
  1. 1. Enumerate dirty files
  2. 2. Classify keep or discard
  3. 3. Re-run validation
  • NOT RUN
    Lane validationnot run
Work orders
WO-002
Assigned
Guardian Not requiredNot connected

mightyprophets-rgb/kleinhub-app-builder · specialist/worktree-triage · first command git status --porcelain

Start proof: none — assignment only, no proven start

Timeline
  • 2026-08-06T17:30:00ZSnapshot reported BLOCKED / dirty.

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