Back to corpus
research noteexperiment writeup candidatescore 32

Operations Hub — iOS Implementation Spec

The web CRM already has two Operations Hub views consolidating all outreach intelligence for a market into a 7-tab surface. The iOS app has the foundation (InboundCommandView, MarketSweepCommandView, InboundService, FieldRoutes) — all connected to the same Supabase. This spec describes the **reorganization + two new hub views** needed to match the web architecture. This is not a ground-up build.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# Operations Hub — iOS Implementation Spec **Date:** 2026-05-28 **Status:** Ready to implement — pass to Codex **Relates to:** Web `PDXSEAOperationsHub.tsx`, `MiamiOperationsHub.tsx` **Supabase project:** `wovknbcvxjvayfdflxkn` The web CRM already has two Operations Hub views consolidating all outreach intelligence for a market into a 7-tab surface. The iOS app has the foundation (InboundCommandView, MarketSweepCommandView, InboundService, FieldRoutes) — all connected to the same Supabase. This spec describes the **reorganization + two new hub views** needed to match the web architecture. This is not a ground-up build. **Real lead counts (verified 2026-05-28 via SQL):** - OR+WA (`inbound_leads` where state IN ('OR','Oregon','WA','Washington')): **1,052 leads**, 100% email, ~87% Instagram - FL (`inbound_leads` where state IN ('FL','Florida')): **700 leads**, 100% email, ~67% Instagram - All markets total: **5,270 leads**, 100% email, 79% Instagram - All `status = 'new'`, zero contacted — full pipeline untouched | Component | File | Status | |---|---|---| | Inbound lead board | `Views/Growth/InboundCommandView.swift` | ✅ Built — flat list, market program selector | | Market sweep command | `Views/Growth/MarketSweepCommandView.swift` | ✅ Built — 7 modes: Sweeps/Markets/Prospects/Outreach/Responses/Sequences/Inbound | | Response inbox | `Views/Growth/ResponseInboxView.swift` | ✅ Built | | Sequence manager | `Views/Growth/SequenceManagerView.swift` | ✅ Built | | Market detail | `Views/Growth/MarketDetailView.swift` | ✅ Built | | Inbound service | `Services/InboundService.swift` | ✅ Built — Supabase bridge for `inbound_leads` | | Field routes + map | `Views/FieldRoutes/` | ✅ Built — cluster map, visit outcomes, day summary | | Visits | `Views/Visits/` | ✅ Built — check-in, revisit list | **What's missing:** Metro/region-grouped contact queues for OR+WA and FL, and a unified hub entry point per market combining map + Instagram + sequences + templates + showcase in one place.

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.