Vendor-agnostic Layer-2 visible alert per spec § P6.A. Subscribes to bus events from BOTH connection.api.hubspot.deal AND connection.api.salesforce.opportunity updates; for each fired record reads the cross-vendor `meeting_to_followup_lag` enrichment via `enrichment-list` with dynamic `{{context.event.payload.platform}}` scope. Dispatches a notification when the meeting → next outbound rep touch lag falls into the `'long'` (≥ 72h / 3d) or `'slipping'` (> 7d) bucket per the value_schema bucket enum (`fast` ≤ 24h / `normal` ≤ 72h / `long` ≤ 7d / `slipping` > 7d / `none` no-followup-yet). The substrate-side housekeeping engagement-aggregates code (D-139 P4 — `backend/server/src/housekeeping/engagement-aggregates/meeting-to-followup-lag.ts`) is the canonical compute path with the full Pass-4 evidence-quality fold (completed-meeting source + outbound rep authorship + lifecycle filter for follow-up evidence states + dedupe_acceptance: 'exact_only').

How it works 8 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Data fetch

▼ lag_rows ?

▼

Process (7 steps)

■ bucket default

Apply default

■ lag_ms default

Apply default

■ deal_name default

Apply default

■ is_overdue compare

Check if bucket is one of long,slipping

■ should_skip compare

Check if is overdue does not equal true

■ notify ?

skip: step.should_skip equal true

■ card to_summary

Format results as a summary card

Settings 1 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

channels setting = in_app