# Signal Re-Activation Plan

Updated: 2026-07-06
Owner: Kisa (STTIL Solutions). Orchestrated by chief-of-staff.
Status: Signal is un-pausing from the clean 2026-06-27 checkpoint. The Insight Engine deadline (2026-07-04) that parked Signal has passed.

This is the umbrella plan. The two technical build plans (01 wiring, 02 completion) sit under it.

## Where Signal actually stands

- Pilot readiness: 13/13 (100%) on the whitepaper checklist.
- Readiness model (dedup + verdict engine) is BUILT and COMMITTED, 57 tests green (verified 2026-07-06), but NOT yet wired into the live pipeline. It is imported nowhere in the backend today.
- Git: clean on main at the 2026-06-27 checkpoint.
- No new inbound leads (the lead table holds only 2 old test rows).

## Core logic: two currencies, run concurrently

Signal's next steps spend two resources that do not compete:

- Product work costs CREW time (agents), not Kisa's. Kisa only reviews and approves.
- The path to a signed pilot costs KISA's time (attorney, Gaboro, labABLE). This, not the product, is the real bottleneck to revenue.

Run both tracks at once. The readiness-model wiring feels like the blocker because it is the visible paused item, but it is off the critical path to a signature. The hosted 13/13 demo is already a sales asset. Keep it green.

Suggested split of Kisa's time over the first two weeks: about 55% revenue and relationships, 35% legal and compliance decisions, 10% product direction and review.

## Critical path to a signed or data-live pilot

Today (IE done, lane frees) -> engage attorney (bundle LOI + NDA + FDA CDS memo + labABLE AKS question into one review pass) in parallel with a value-led Gaboro re-approach (EO / AI-compliance angle, not the pilot ask) -> attorney-cleared LOI and NDA + Gaboro re-warmed -> Gaboro pilot interest confirmed -> NDA and LOI executed -> pilot-gate compliance cleared (MFA verify, retention doc, deletion test) -> data-live pilot.

The attorney is the long pole. The only lever is starting the clock early. Product wiring runs beside this chain on crew time. It must be done before real data flows, but it does not gate the signature.

## Day-1 moves

1. Confirm Insight Engine is done, freeing the single-project lane, then flip Signal to active.
2. One attorney email (Kisa): LOI template + NDA template + FDA CDS memo + labABLE kit-in-kit AKS question, in a single review pass, asking for a turnaround estimate. Fine to have it passed to an associate.
3. Decide: send the Convex BAA email, or park it. The Convex spike is designed and waiting on that one email.

First crew action the moment the lane is free: lead-signal wires the readiness model live (plan 01), with an independent code-auditor pass and a live-verify before it is called done.

## Sequence (owners and gates)

### Week 1
- P1 wire readiness model into the live pipeline. Owner: lead-signal (crew). Entry: clean checkpoint + lane free. Exit: railway deploy confirmed live + code-auditor PASS + live-verify PASS. Plan: docs/build-plans/01-readiness-model-wiring.md
- P2 citation IDs in payer_rules.json. Owner: lead-signal (crew).
- C1 PostgreSQL 6-year audit-retention doc. Owner: lead-infrastructure (crew).
- C2 MFA verified on all 5 admin accounts (AWS, Supabase, Railway, Vercel, Clerk). Owner: lead-infrastructure + Kisa (her own accounts).
- C10 production access scope doc. Owner: lead-infrastructure (crew).
- C11 CMS AI-governance quarterly monitoring cadence. Owner: lead-sttil (crew).
- C3 FDA CDS exemption memo: draft (crew, Fable) then attorney review (Kisa). Draft: docs/compliance/fda-cds-exemption-memo-DRAFT.md
- C4 + C5 send LOI and NDA templates to attorney. Owner: Kisa.
- C12 engage attorney on the labABLE kit-in-kit AKS question. Owner: Kisa (same email).
- R1 schedule and hold the labABLE follow-up call. Owner: Kisa.
- I2 Kisa sends the Convex BAA email; lead-infrastructure starts signal-convex Phase 1.
- R2-prep Gaboro re-engagement positioning (EO / AI angle, value-led, no ask). Owner: growth-marketer (crew), draft only.

### Week 2
- P3 patient rollup, P4 device override, P5 plan-type enforcement, P6 frontend nesting. Owner: lead-signal (crew). Plan: docs/build-plans/02-readiness-model-completion.md. P6 needs a Kisa-approved mockup first.
- C8 deletion procedure tested against the Gaboro test batch. Owner: lead-signal (crew).
- C9 internal tabletop incident exercise. Owner: lead-sttil facilitates + Kisa participates.
- I1 data-platform decision (repaired-NocoDB / Supabase / Neon / AWS / Convex). Owner: cto-architect decides, lead-infrastructure briefs.
- R2-send Kisa re-engages Gaboro.
- R3-kickoff waitlist landing page + billing-company ICP. Owner: lead-content + growth-marketer (crew).

### Backlog / attorney-gated
- C6 LOI executed, C7 NDA executed (Kisa, after the attorney clears the templates).
- I2-complete Convex spike phases 2 and 3.
- R3-build waitlist page built and published.
- C3-review attorney returns the FDA memo; C12-result AKS guidance received.

## The labABLE vs Gaboro call

Lead with Gaboro, the only real DMEPOS pilot path. Keep labABLE warm on a low-cost cadence (the follow-up call). labABLE's LOI is signed and it is a strategic channel, but any deepening is gated on the AKS review anyway, so leaning in cannot make it move faster. Bank Mehul's ICP advice (shift toward billing companies, waitlist, attach-to-software) for a post-reactivation strategy review. Do not let it pull the sprint off Gaboro.

## Guardrail against compliance scope sprawl

Split the first-supplier gate into "needed before a signature" (LOI and NDA reviewed and executed) versus "needed before real data flows" (MFA, retention, deletion test, tabletop). Only front-load the signature-gating subset. All legal rulings stay with the human attorney.

## Grounded findings from the 2026-07-06 build-plan capture

- plan_type is never ingested by the normalizer today, so the moment the readiness model goes live, every patient reads "Plan Type Needed". Fix (small, written into plan 01): ingest a supplier-mapped plan_type column, verbatim, never guessed, and ship it with the wiring.
- Readiness + dedup engine = 57 tests green (verified 2026-07-06). The "73 tests" figure in current-state.md is stale. Correct it at the next state-sync.
- P6 (worklist redesign) needs a rendered mockup Kisa approves before any code (nesting layout, "Plan Type Needed" badge, legend, export granularity).
- P4 "device override" definition: the plan follows the locked phase-2 design (a device-keyed staff override that fixes the doc_status override leak), not per-device rule config. Confirm before building P4.

## Related files

- docs/build-plans/01-readiness-model-wiring.md
- docs/build-plans/02-readiness-model-completion.md
- docs/compliance/fda-cds-exemption-memo-DRAFT.md (draft, attorney review pending)
- context/current-state.md (canonical volatile state)
- context/vc-traction.md (investor and pilot relationships)
- CLAUDE.md (pilot readiness + compliance checklists)