What happened: Sync pending.
Who it affects: Internal auditors on Audit & Assurance.
Proven so far: Snapshot reports a sync-pending / ahead-docs state.
Best guess, not proven: Documentation committed ahead of the lane sync (suspected).
Still unknown: Whether any audit verdict depends on the unsynced docs.
A worker moves this next; you do not need to do anything.
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
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
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
- Detect
- Triage
- Diagnose
- Guardian check
- Assign specialist
- Owner GO
- Repair
- Test
- Audit
- Guardian recheck
- Recovery watch
- Discharge
Pulse snapshot · audit-assurance · Recent · 2026-08-06 17:30 UTC · Known
- • Sync pending
- • Docs ahead of lane
- • Snapshot reports a sync-pending / ahead-docs state.
- • Documentation committed ahead of the lane sync (suspected).
- • Whether any audit verdict depends on the unsynced docs.
customer Impact
None observed
data Risk
None observed
security Risk
None observed
revenue Impact
None observed
operational Impact
Audit records may not match the synced lane state.
release Impact
None observed
blast Radius
Audit lane
time Sensitivity
Low
Affected users: Internal auditors
Affected systems: Audit & Assurance lane
Rollback baseline: Last synced Audit commit
Audit verdict: Self-reported
Guardian recheck: Not required
Recovery watch: Not started
Discharge proof: None recorded
- 1. Reconcile docs with lane
- 2. Re-sync
- 3. Confirm verdicts unaffected
No tests defined yet.
mightyprophets-rgb/kleinhub-assurance-hub · main · first command git log --oneline -n 20
Start proof: none — assignment only, no proven start
- 2026-08-06T17:30:00ZAhead-docs state observed.
Read-only view. Pulse never publishes, deploys, migrates or clears a Guardian gate.