docs+state: Convex-Signal spike brief + ship-status ledger + session wrap [CC]

- docs/convex-signal-instance-brief-2026-06-24.md: modular, backend-swappable Convex spike brief (separate repo signal-convex)
- docs/ship-status-ledger.md: committed shipped/not-shipped/why ledger, shared with Pi
- context/current-state.md: session wrap (delegation trigger shipped, NocoDB diagnosed, Convex eval)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

context/current-state.md

@@ -2,45 +2,41 @@ v:1
 
 # current-state
 
-ACTIVE: Both Pi design tasks delivered: (1) delegation-router full system (design doc + Pi trigger extension + 2 skills), (2) Option B research artifact versioning (design doc + Pi auto-stage extension + research-versioning skill + content dir). All Pi-side code is live — Pi has enabled the dispatch-trigger and research-versioning extensions. Claude builds from both design docs.
-NEXT (agent, in order): (1) Claude: build the Claude-side trigger from Pi's design doc at docs/delegation-router-design-2026-06-24.md (dispatch-trigger.sh + settings.json UserPromptSubmit hook + dispatch threshold edits to dispatch SKILL.md). (2) Claude: build the research-auto from Pi's design doc at docs/research-versioning-design-2026-06-24.md (research-autopush.sh + settings.json Stop hook entry + content/ dir). (3) Claude: build the readiness model (rename coverage->readiness, rules-to-config, patient/line/shipment grouping + verdict, device-keyed override+recompute, require-plan-type + remove guesser, frontend nesting). (4) Claude: review Pi's AIOS + Automated Blog plans and recommend. (5) Kisa: /pilot-prep for labABLE Fri 2026-06-26 1:30 PM. MCP parity + skills-as-git-repo = phase 2.
+ACTIVE: Claude SHIPPED + verified the Claude-side delegation trigger (caught + fixed Pi's $1->stdin bug and the Finding-4 dispatch-rule conflict; verified firing live). Diagnosed the NocoDB leads failure: the Signal base's data source is corrupted and creates PK-less tables (capture still works, delete/update don't). Ran a full Convex platform evaluation (Professional $25/dev/mo includes the BAA + HIPAA/SOC2 + daily backups, NOT Enterprise-gated; leads are PII-not-PHI so they stay outside the PHI boundary). Wrote the Convex-Signal spike brief and created a committed ship-status ledger (docs/ship-status-ledger.md).
+
+NEXT (in order): (1) Kisa: dedup decision (same patient + device + DOS under two order numbers -> one worklist line or two?) -> unblocks Claude's readiness-model build. (2) Pi: design the modular Convex-Signal spike from docs/convex-signal-instance-brief-2026-06-24.md (separate repo signal-convex; swappable auth + data layer; reuse the readiness model). (3) Kisa: send the Convex BAA email + /pilot-prep labABLE Fri 2026-06-26 1:30 PM. (4) Claude: build the readiness model once dedup is decided. (5) Claude: research-versioning Layer-1 + add signal/docs/ to its scope (Audit Finding 5 — the reason design docs need manual commits). (6) After Pi's Convex design + Kisa approval: create signal-convex (Claude=GitHub, Forgejo needs Kisa/token), Claude builds the spike. FULL ship-status + reasons/dependencies: docs/ship-status-ledger.md.
 
 ## Decisions (last 8)
 
-- 2026-06-24 [Pi]: Option B research artifact auto-versioning designed and persisted to docs/research-versioning-design-2026-06-24.md. Pi-side extension (research-versioning.ts) auto-stages research files on write. Skill (research-versioning) added to shared skills. Content dir (signal/content/blog/) created. Claude builds research-autopush.sh + settings.json hook entry.
-- 2026-06-24 [Pi]: Delegation router full design persisted to docs/delegation-router-design-2026-06-24.md (trigger keyword sets + injected text + hook config + dispatch thresholds + Pi-side mirror extension + two process skills). Pi-side trigger extension written to ~/.pi/agent/extensions/dispatch-trigger.ts (before_agent_start event, keyword heuristics). Skills deployed: delegation-discipline (shared tier 2) + design-review-persist (fixes the persist gap — Pi writes files before declaring done). Claude builds Claude-side trigger + threshold edits from the design doc.
-- 2026-06-24 [CC]: AIOS-as-a-consulting-business PARKED (pipeline, not ruled out) per Kisa + problem-solver. Signal stays the product; AIOS *thinking* (connectors, internal OS, automated blog) stays active. Activate only on demand-pull + Signal self-sustaining (~2-3 paying contracts) + delegable capacity. Memory: project_aios_consulting_parked. Next groundwork: the automated SEO blog (coach-endorsed, compounds for Signal).
-- 2026-06-24 [CC]: AUDIT for missed Pi cues. Pi made ZERO file-writes across all its sessions; recovered its Signal AIOS + Automated Blog plans from session log 019ef117 to docs/aios-and-blog-2026-06-22-pi-recovered.md. Shield is persisted (file + rich TriLane compliance/competitor research). Kisa's goal: a sellable Signal AIOS; interpretation fork + sttil-compliance-check gate pending before groundwork.
-- 2026-06-24 [CC]: Delegation made automatic + content-driven (Kisa's call, worked via /barrier). The existing `dispatch` skill is the router brain (no new skill); trigger = a cheap UserPromptSubmit keyword hook (Route 2, no LLM cost) firing dispatch only on task-shaped prompts; chief-of-staff stays conditional (hat chosen by the task, never permanent, never forbidden). Hybrid 3-tier skill model locked. Briefed to Pi at docs/delegation-and-skills-brief-2026-06-24.md.
-- 2026-06-24 [CC]: Applied the startup edits — build complete. Global CLAUDE.md Step 1 now runs the state-sync read of current-state.md; Pi AGENTS.md embedded state block demoted to a pointer, skill section modernized, state-sync added. Backups at *.bak-2026-06-24. Workflow-consolidation core: schema + skill + governance + demoted blocks + auto-push hook + startup edits, all done.
-- 2026-06-24 [CC]: Built + activated the scoped auto-push Stop hook (~/.claude/hooks/state-autopush.sh + ~/.claude/settings.json Stop) — commits + pushes current-state.md only on session stop, never `git add .`. Push path verified. Kisa chose hook option a; option b (broaden auto-versioning to research artifacts) handed to Pi to re-design for the research workflow.
-- 2026-06-24 [CC]: Recovered Pi's workflow-consolidation design from its session log (Pi finalized it in chat but never wrote it to a file) to docs/workflow-consolidation-design-2026-06-24-pi-recovered.md. Built v:1 state schema + state-sync skill + governance doc; demoted CLAUDE.md embedded state block. Corrected Pi's Stop hook to scope to current-state.md, not `git add .`.
-- 2026-06-24 [Pi]: Workflow consolidation design completed (v:1 schema, read/write + commit/push protocol, Stop-hook automation, skills + MCP parity, drift-to-skill table, universal git versioning). Ready for Claude implementation.
-- 2026-06-23 [CC]: Workflow-consolidation brief handed to Pi (architect-reviewed); clean-start commit of current-state.md, context recovery artifacts gitignored, pushed to Forgejo + GitHub.
-- 2026-06-23 [CC]: Readiness model redesign locked. Signal never determines/guesses payer plan type, eligibility, or coverage; client supplies plan type as a required mapped field; every determination cites the rule + client input. Worklist = one record per patient UUID with per-device CoverageLines; verdict from required-vs-supplied. "coverage" renamed "readiness". Brief: docs/readiness-model-brief-2026-06-23.md.
-- 2026-06-23 [Pi]: RAP-ID/CSP-ID architecture proposed to reconcile rotating anonymous patient ID with persistent worklist. SaaS web app hosted by STTIL; client holds Real-ID to CSP-ID map; HIPAA host (Validated Cloud) still required.
-- 2026-06-23 [Pi]: Shield architecture designed (standalone compliance product, tiered deployment, AI Consent Addendum). Ready for Claude build or refinement.
-- 2026-06-23 [CC]: DNSSEC verified live. Website agent-file compliance fixes staged locally (removed outreach wording, banned >25% stat, exposed pricing, SWO term fixed) — NOT deployed; prose rewrites routed to lead-content.
-- 2026-06-22 [CC]: Build Spec Phase 2 built; Clerk prod migration complete (pk_live on Vercel + JWKS on Railway). Phase 4 (support bot foundation) spec by Pi ready for build.
+- 2026-06-24 [CC]: SHIPPED the Claude-side delegation trigger — dispatch-trigger.sh reads stdin JSON (fixed Pi's $1 bug), settings.json UserPromptSubmit hook wired, dispatch SKILL.md thresholds added, Finding-4 clarifying line so old+new dispatch rules don't conflict. Verified live. Audit Findings 1/2/4 (this build) closed; 3/8 Pi-side, 5/6/7/9 research-versioning/phase-2 and non-blocking.
+- 2026-06-24 [CC]: NocoDB leads diagnosed — Signal-base data source bdmhi02nks1pg6g is corrupted, creates PK-less tables (old leads + a fresh test table both no-PK; content base healthy). SQLite can't add a PK to a populated table (Route 1 failed). Capture still works (n8n webhook signal-cgm-lead inserts ok); 2 test rows un-deletable. Folded into the platform decision.
+- 2026-06-24 [CC]: Convex evaluation (verified). Professional $25/dev/mo includes BAA + HIPAA/SOC2 reports + daily backups (NOT Enterprise). Leads = PII-not-PHI -> outside the PHI/Validated-Cloud boundary. AWS (BAA + RDS/S3 provisioned, parked) = proven fallback; Neon = cheaper managed Postgres. Decision: build a SEPARATE 'Signal on Convex' spike (repo signal-convex), modular + backend-swappable to limit lock-in. Brief: docs/convex-signal-instance-brief-2026-06-24.md.
+- 2026-06-24 [CC/Kisa]: Operating principle locked — ship-status + reason/dependency for anything unbuilt lives in git (docs/ship-status-ledger.md), NOT private memory, so Pi + Claude + Kisa all see what shipped and why/why-not. Kisa validates; the two agents reason next steps.
+- 2026-06-24 [Pi]: Option B research artifact auto-versioning designed and persisted to docs/research-versioning-design-2026-06-24.md. Pi-side extension (research-versioning.ts) auto-stages research files on write. Skill (research-versioning) added. Content dir (signal/content/blog/) created. Claude builds research-autopush.sh + Stop-hook entry.
+- 2026-06-24 [Pi]: Delegation router full design persisted to docs/delegation-router-design-2026-06-24.md (trigger keyword sets + injected text + hook config + dispatch thresholds + Pi-side mirror extension + two process skills). Skills deployed: delegation-discipline + design-review-persist.
+- 2026-06-24 [CC]: AIOS-as-a-consulting-business PARKED (pipeline, not ruled out). Signal stays the product; AIOS thinking stays active. Activate only on demand-pull + Signal self-sustaining (~2-3 paying contracts) + delegable capacity. Memory: project_aios_consulting_parked.
+- 2026-06-23 [CC]: Readiness model redesign locked. Signal never determines/guesses payer plan type, eligibility, or coverage; client supplies plan type as a required mapped field; every determination cites the rule + client input. Worklist = one record per patient UUID with per-device CoverageLines; verdict from required-vs-supplied. Brief: docs/readiness-model-brief-2026-06-23.md.
 
 ## Open Threads (max 5)
 
-- WORKFLOW CONSOLIDATION (2026-06-24): building from Pi's recovered design. Remaining: Stop hook (Kisa review), global CLAUDE.md + Pi AGENTS.md startup edits, MCP parity, optional skills-as-git-repo. Design: docs/workflow-consolidation-design-2026-06-24-pi-recovered.md; brief: docs/workflow-consolidation-brief-2026-06-23.md.
-- READINESS MODEL BUILD (2026-06-23): Pi's build design ready; Claude builds the rename + rules-to-config + grouping/verdict sequence. Brief: docs/readiness-model-brief-2026-06-23.md.
-- SIGNAL AIOS PRODUCT (2026-06-24): Kisa's goal = build a sellable Signal AIOS. Pi's plans RECOVERED to docs/aios-and-blog-2026-06-22-pi-recovered.md (Pi wrote zero files). Shield has a file + TriLane research; accelerator AIOS lessons in vault. Groundwork pending: resolve interpretation (premium tier ON Signal vs Signal-as-AIOS), sttil-compliance-check gate, product + positioning (multi-division -> crew).
+- CONVEX-SIGNAL SPIKE (2026-06-24): brief ready (docs/convex-signal-instance-brief-2026-06-24.md); separate repo signal-convex; Pi designs next. Deps: Kisa's Convex BAA email; repo creation post-approval. Goal: prove Convex on the real product, low-risk parallel, before any platform commitment.
+- DATA-PLATFORM DECISION (2026-06-24): NocoDB leads broke (no-PK, corrupted source). Options: repaired-NocoDB / Supabase Postgres / Neon / AWS (already set up) / Convex. Leads = non-PHI. Informed by the Convex spike. Interim: capture works; 2 test rows un-deletable.
+- READINESS MODEL BUILD: BLOCKED on Kisa's dedup decision. Design ready: docs/readiness-model-brief-2026-06-23.md.
+- DELEGATION / RESEARCH-VERSIONING CLEANUP: trigger SHIPPED; remaining = research-versioning Layer-1 + signal/docs scope (Finding 5), low-priority Findings 6/7/9, Pi-side 3/8. Ledger: docs/ship-status-ledger.md.
 - LabABLE Meeting Fri 2026-06-26 1:30 PM — /pilot-prep.
-- Website copy: brief lead-content for human-page rewrites (extract eligibility/coverage language); deploy staged agent-file fixes; 6-year retention doc fix. BAA wording attorney-gated.
 
 ## Stack
 
-- Signal: PHI contained in `patient_id` (name, MRN, account #s) — tokenization via RAP-ID/CSP-ID (rotating anonymous ID, not static UUID).
+- Signal: PHI contained in `patient_id` (name, MRN, account #s) — tokenization via RAP-ID/CSP-ID (rotating anonymous ID, not static UUID). Real PHI currently BLOCKED/mock — no active exposure.
 - Signal-api: Railway (signal-api-production-91c2). Signal-ui: Vercel (signal-ui-xi.vercel.app). Supabase: itmospnregdyiatbbdwl (JWT key).
 - Clerk: production key on Vercel + Railway; frontend auth via clerk.sttilsolutions.com; Google OAuth configured.
+- Leads: website form -> n8n webhook (n8n.sttilsolutions.com/webhook/signal-cgm-lead) -> NocoDB (Signal base source corrupted, no-PK; capture works, cleanup blocked). Convex spike + platform decision pending.
+- Compliant fallback: AWS BAA signed 2026-05-27, RDS (signal-db) + S3 provisioned, parked. Convex Professional $25/mo = BAA-capable alternative under evaluation.
 - TriLane: localhost:8000 (signal/sessions/scale-software). Pi reaches it over HTTP (127.0.0.1:8000); contract in trilane/TRILANE_HTTP_API.md.
 - Model for Pi: deepseek/deepseek-v4-flash.
 
 ## Tip
 
-State protocol: read = `git pull --rebase` then read this file (warn if Updated > 24h old); write = edit ACTIVE/NEXT, append one author-stamped decision, then commit + push. Full protocol in the `state-sync` skill. TriLane = searchable archive, not live state.
+State protocol: read = `git pull --rebase` then read this file (warn if Updated > 24h old); write = edit ACTIVE/NEXT, append one author-stamped decision, then commit + push. Full protocol in the `state-sync` skill. Detailed ship-status (what shipped / didn't / why) = docs/ship-status-ledger.md. TriLane = searchable archive, not live state.
 
-## Updated: 2026-06-24 (Pi: session resume + continue. Both Pi design tasks delivered: delegation router system and Option B research artifact versioning. Pi made 8 file writes this session — the persist gap is closed.)
+## Updated: 2026-06-24 (CC: session wrap. Delegation trigger SHIPPED + verified; NocoDB leads diagnosed; full Convex evaluation ($25/mo Professional incl BAA) + spike brief; ship-status ledger created at docs/ship-status-ledger.md.)

docs/convex-signal-instance-brief-2026-06-24.md

@@ -0,0 +1,71 @@
+# Brief for Pi — Modular Convex-Based Signal Instance (Parallel Experiment)
+
+**Date:** 2026-06-24
+**From:** Claude (synthesizing Kisa's direction)
+**For:** Pi (produce the build design from this brief; then Claude builds)
+**Approves:** Kisa
+**Status:** Design input. This is a SEPARATE, parallel instance. Nothing in the current build is abandoned or touched.
+
+---
+
+## 1. Objective
+
+Design a **modular, backend-swappable architecture** for a separate "Signal on Convex" instance — an experimental alternative to the current Railway/Supabase/Vercel/Clerk stack — that exploits Convex's reactive platform and its affordable HIPAA path, while keeping the design portable enough that the backend (Convex / AWS RDS / Neon Postgres) is a config choice, not a rewrite.
+
+This is a **parallel R&D track**, not a migration. The live Signal build keeps running and keeps being developed. This proves Convex on the real product before any commitment.
+
+## 2. Why (strategic context)
+
+- **Current stack** is not HIPAA-capable for real PHI (Railway has no BAA; Supabase Pro has no HIPAA tier). PHI is currently mock/synthetic and deferred. The compliance risk is latent, not active.
+- **Convex (verified 2026-06-24):** reactive TypeScript backend. **BAA + HIPAA/SOC 2 reports + daily backups are on the Professional plan at $25/developer/month** — not gated behind Enterprise. SOC 2 Type II, AWS-hosted, GDPR. Built-in: server functions, crons, file storage, vector search, auth, audit log. Open-source / self-hostable. Ships **Convex Components** = independent, modular, TypeScript building blocks.
+- **The prize:** one managed platform at ~$25/mo that could collapse today's patchwork (backend + DB + storage + automation + the future compliance host) into a single BAA-covered home — and avoid the AWS complexity Kisa wants to avoid.
+- **The fallback (already built):** AWS — BAA signed 2026-05-27, RDS + S3 provisioned, currently parked. Proven, break-glass. Neon (managed Postgres, HIPAA on Scale, scale-to-zero) is a cheaper managed-Postgres fallback.
+- **The one real risk:** Convex vendor lock-in (proprietary reactive layer). The modularity + swappable data layer below is the deliberate hedge.
+
+## 3. Modularity requirements (Kisa's explicit ask)
+
+Modular where it adds value and stays cohesive. **Not** so granular it's hard to build. Pragmatic seams, one coherent whole.
+
+Required modular seams:
+1. **Auth / login module** — designed behind a seam so it can be **Convex auth OR Clerk** (we already run Clerk in production). Pick a default, but keep the seam clean so swapping is config, not rewrite.
+2. **Data-access layer (the keystone)** — all reads/writes go through a clean interface so the persistence backend (**Convex / AWS RDS / Neon Postgres**) is interchangeable. This is the primary lock-in hedge. Note Convex's BYOD-Postgres option as a further mitigation.
+3. **Readiness-rules engine** — the gap/verdict logic as a self-contained module (reuse the existing rules-as-addressable-config direction + `payer_rules.json`), so it is portable across instances and reusable across the STTIL portfolio (and the future Med Tracker).
+4. **Document / file storage module** — behind a seam (Convex file storage vs S3).
+5. **Automations module** — scheduled checks / crons as discrete, named jobs.
+6. **Notifications module** — new-lead / worklist alerts, swappable transport (matches existing n8n + NavBot patterns).
+
+Use **Convex Components** where they map cleanly to these seams. Keep it cohesive — favor a small number of meaningful modules over many micro-modules.
+
+## 4. Same architecture strategy (git / skills / workflow)
+
+The Convex instance must fit STTIL's existing operating model, not invent a new one:
+- **Git-versioned in a SEPARATE repo `signal-convex`** (Forgejo source of truth + GitHub, per the `git-push` convention; check Forgejo for an existing repo first). Decided 2026-06-24: a separate repo, NOT a directory in the existing build, so the experiment can never be confused with or break the pilot-critical live Signal repo. Shared logic (readiness rules + `payer_rules.json`) is COPIED into the spike for now; extract a shared package only if both instances graduate.
+- **Pi designs → Claude builds.** Pi persists this design to a file (`design-review-persist` skill); state tracked in `context/current-state.md` via `state-sync`; design docs versioned per `research-versioning`.
+- **Implements the SAME readiness model** as the current build (per `readiness-model-brief-2026-06-23.md`): plan-type is a required client-supplied field (never guessed), required-vs-supplied verdict that kills the false green, patient → device-line → shipment grouping, citations on every determination. The Convex instance re-expresses this model on Convex, it does not redesign it.
+- **Compliance alignment:** rotating anonymous patient ID direction; human-in-the-loop preserved; built-in audit log; non-PHI stays out of the PHI boundary; **BAA must be signed before any real PHI touches it.** Map to the `project_signal_compliance_architecture` direction (EO on AI + identifiable health data, local inference where relevant, API-first connectors). Flag where `sttil-compliance-check` + attorney sign-off are required.
+
+## 5. What Pi should design / deliver
+
+1. The module map: the seams from §3, their boundaries, and how they stay cohesive (a diagram + an analogy per `feedback_analogical_explainer`).
+2. The data-access interface that makes Convex / RDS / Neon swappable (the lock-in hedge), including the BYOD-Postgres note.
+3. The Convex schema + function structure for the readiness model.
+4. The auth seam (Convex auth vs Clerk) with a recommended default.
+5. How it reuses the existing readiness logic + `payer_rules.json` rather than re-inventing it.
+6. Repo structure + how it plugs into git / skills / state-sync / Pi-builds-Claude workflow.
+7. Compliance touchpoints + the explicit "needs BAA / attorney / compliance-check before PHI" list.
+8. A **phased, timeboxed spike plan** (prove the core readiness loop + auth seam + data-layer swappability first), sized so it does NOT eat pilot or readiness-model time.
+9. Effort estimate + an explicit "what Claude builds first."
+
+## 6. Out of scope (keep it a spike, not a rebuild)
+
+- No real PHI until the Convex BAA is signed.
+- Do not touch or migrate the existing live build.
+- No full feature parity in v1 — prove the core loop + the two key seams (auth, data layer).
+- No over-granular micro-modularization.
+- Final PHI-backend decision (Convex vs AWS vs Neon vs "Validated Cloud") is NOT made here — this spike produces the evidence for it.
+
+## 7. Open questions for Pi to resolve
+
+- Convex auth vs keep Clerk as the default for the spike?
+- Dedup key decision still open from the readiness model (same patient + device + DOS under two order numbers → one line or two?) — carry the same resolution here.
+- Where the data-access interface boundary should sit to keep Convex's reactivity benefit while preserving swappability (the real design tension — reactivity is Convex-specific; flag honestly how much portability costs).

docs/ship-status-ledger.md

@@ -0,0 +1,51 @@
+# Signal — Ship-Status Ledger
+
+Canonical, git-tracked record of **what shipped, what didn't, and the reason or dependency** for anything outstanding. Both Pi and Claude read and maintain this; Kisa validates. Ship-status never lives only in private memory. Update this on every ship or blocker change. Pairs with `context/current-state.md` (this = the detailed ledger; current-state = the live ACTIVE/NEXT snapshot).
+
+**Status legend:** SHIPPED · IN PROGRESS · BLOCKED · NOT STARTED · DEFERRED · PI-SIDE · PARKED
+
+---
+
+## Ledger (as of 2026-06-24)
+
+| # | Item | Owner | Status | Reason / Dependency | Next action |
+|---|------|-------|--------|---------------------|-------------|
+| 1 | Claude-side delegation trigger (`dispatch-trigger.sh` + settings.json `UserPromptSubmit` hook + dispatch thresholds) | Claude | **SHIPPED** (verified live) | none | done |
+| 2 | Audit Finding 1 — hook stdout injection works | Claude | **SHIPPED** | verified live (marker reached the model) | done |
+| 3 | Audit Finding 2 — `$1` bug → read stdin JSON | Claude | **SHIPPED** | caught + fixed during build | done |
+| 4 | Audit Finding 4 — old+new dispatch rules conflict | Claude | **SHIPPED** | added clarifying line (kept judgment fallback, marker = evaluate not auto-dispatch) | done |
+| 5 | Convex-Signal spike **brief** | Claude | **SHIPPED** (committed this wrap) | — | Pi designs from it |
+| 6 | Convex-Signal spike **design** | Pi | **NOT STARTED** | Dependency: brief (item 5, ready). Safe to start now. | hand brief to Pi |
+| 7 | `signal-convex` repo creation | Claude (GitHub) + Kisa/token (Forgejo) | **PENDING** | Dependency: Pi design + Kisa approval (create once, correctly). Claude can do GitHub via `gh`; Forgejo has no API token here. | after design approved |
+| 8 | Convex BAA email (plan/cost/signing) | Kisa | **IN PROGRESS** | Kisa handling | Kisa sends |
+| 9 | Readiness-model build (rename coverage→readiness, rules-to-config, grouping+verdict, device override, require-plan-type, frontend nesting) | Claude | **BLOCKED** | Dependency: Kisa's dedup decision (same patient + device + DOS under two order numbers → one worklist line or two?). Design ready: `docs/readiness-model-brief-2026-06-23.md` | Kisa decides → Claude builds |
+| 10 | NocoDB leads / CRM cleanup | Claude + Kisa | **BLOCKED** | Reason: leads table has no primary key (Signal-base data source `bdmhi02nks1pg6g` is corrupted — a fresh table there also came up PK-less; content base is healthy). SQLite can't add a PK to a populated table (Route 1 failed). Interim: capture still works (inserts via n8n `signal-cgm-lead`); the 2 test rows can't be deleted. | resolved by the data-platform decision (item 11) |
+| 11 | Data-platform decision (leads + future PHI backend) | Kisa (with Claude/Pi analysis) | **OPEN** | Options analyzed: repaired-NocoDB / Supabase Postgres / Neon / AWS (already set up, BAA+RDS+S3 parked) / Convex ($25/mo incl. BAA). Leads = non-PHI (stay outside PHI boundary). Decision informed by the Convex spike. | run spike → decide |
+| 12 | Research-versioning Layer-1 (`research-autopush.sh` + Stop-hook entry) | Claude | **NOT STARTED** | Dependency: Pi design exists (`docs/research-versioning-design-2026-06-24.md`). Lower priority than product. | next infra slot |
+| 13 | `signal/docs/` auto-versioning (Audit Finding 5) | Claude + Pi | **NOT BUILT** | Reason: research-versioning scope excludes `signal/docs/`. **This is why design docs need manual commits.** | add `signal/docs/` to scope |
+| 14 | Pi research-versioning ext `tool_call`→`tool_result` (Finding 3) | Pi | **LIKELY DONE** | Pi state reports persist gap closed (8 file writes this session); confirm it is the tool_result fix | Pi confirm |
+| 15 | Mid-session commit push on clean tree (Finding 6) | Claude | **DEFERRED** | optional, low risk, adds session-close latency | revisit if loss occurs |
+| 16 | Chief-of-staff sequential-dependency capability (Finding 7) | Claude | **NOT TESTED** | Dependency: a discovery test with a sequential multi-specialist brief | run the test |
+| 17 | Pi injected-message behavior (Finding 8) | Pi | **NOT TESTED** | Pi-side test | Pi test |
+| 18 | Skills-as-git-repo (Finding 9) | Claude/Pi | **DEFERRED** | Phase 2 per workflow-consolidation plan | phase 2 |
+| 19 | Website copy + agent-file fixes | lead-content / Claude | **STAGED, not deployed** | prose rewrites routed to lead-content; BAA wording attorney-gated | deploy when ready |
+| 20 | Signal AIOS product | — | **PARKED** | Activate only on demand-pull + Signal self-sustaining + delegable capacity | hold |
+
+---
+
+## Timeline / critical path
+
+1. **Next session:** (a) Kisa gives the dedup decision → Claude builds the readiness model (item 9). (b) In parallel, Pi designs the Convex-Signal spike from the committed brief (item 6).
+2. **After Pi's Convex design:** Kisa validates → create `signal-convex` (item 7) → Claude builds the spike.
+3. **Convex spike + BAA terms (item 8)** → inform the data-platform decision (item 11) → which resolves the NocoDB leads/CRM fix (item 10).
+4. **Infra cleanup (batched in slack):** research-versioning Layer-1 + `signal/docs/` scope (items 12–13, the reason docs need manual commits), then low-priority Findings 6/7/9. Findings 3/8 are Pi-side.
+5. **Fixed date:** labABLE `/pilot-prep` Fri 2026-06-26 1:30 PM.
+
+## Dependencies summary
+- Readiness build ⟸ Kisa dedup decision.
+- Convex spike build ⟸ Pi design ⟸ committed brief (ready) ; and ⟸ Kisa approval + repo creation.
+- NocoDB/leads fix ⟸ data-platform decision ⟸ Convex spike evidence + BAA terms.
+- Design-doc durability ⟸ `signal/docs/` auto-versioning (until built, commit docs manually).
+
+## Maintenance
+Update this whenever an item ships or a blocker changes. Move shipped items to a `## Shipped (archive)` section when the table grows. Both agents reason from this; Kisa validates and redirects.

test-data/sample-green.csv

@@ -0,0 +1,2 @@
+patient_id,device_type,shipment_date,quantity,payer,visit_date,swo_status,pecos_verified,pa_status,diagnosis_on_file
+PT-GREEN-1,dexcom_g7,2026-06-10,3,Medicare Part B,2026-04-15,On File,Yes,Not Required,Yes