--- title: Plans inventory last_verified: 2026-05-05 verification_type: eyeball verification_ttl_days: 30 status: active --- # `docs/plans/` — inventory > **This file is the single source of truth for plan status in this repo.** When a plan changes status, update the row here. Do NOT mirror status into CLAUDE.md, the plan's own header, or any other tracker. > > **Operating rules** for what counts as a plan, where to put it, and how to name it: see `CLAUDE.md` → "Planning & project docs." ## Active plans | Plan | Status | Owner | Created | Last updated | Blocks | Blocked by | Summary | | ---------------------------------------------------------------------------- | ----------------------------- | ----- | ---------- | ------------ | -------------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | [`claude-after-dark.md`](claude-after-dark.md) | active | Kyle | 2026-04-28 | 2026-04-29 | — | — | Implementation plan for the overnight Claude Code automation system + repo-as-source-of-truth discipline. Governs `.github/workflows/claude-overnight.yml` and the `.claude/agents/` fleet. Track A (docs) blocked on team onboarding; Track B (automation) running solo. | | [`magic-link-portal-login.md`](magic-link-portal-login.md) | active | Kyle | 2026-04-27 | 2026-04-27 | `refill-conversion/` (replaces stages 5–6 of the funnel) | Compliance counsel sign-off | Pre-implementation lead-developer handoff for SMS + email magic-link auth into the B2B Commerce portal (OAuth 2.0 JWT Bearer + `/services/oauth2/singleaccess`). Pre-build. | | [`multi-sandbox-kit.md`](multi-sandbox-kit.md) | active | Kyle | 2026-05-05 | 2026-05-05 | — | Prod read-access via Integration User pattern | Plan to reframe the knowledge kit so prod is the canonical wiki and sandboxes are disposable workspaces. Not yet executed. | | [`refill-conversion/`](refill-conversion/) | active (Phase 1 in progress) | Kyle | 2026-04-27 | 2026-04-27 | Phase 2 intervention design (downstream) | Sandbox-data constraint (Phase 1 deliverable #5 may defer numbers) | Phase 1 current-state audit: diagnose where in the 12-stage funnel patients drop off between refill reminder and completed portal order. Five-file investigation: README + cohort-definition + measurability-matrix + gap-list + baseline-analysis. | | [`azure-structured-intake-writes/`](azure-structured-intake-writes/) | active (Phase A0 done) | Kyle | 2026-05-06 | 2026-05-09 | NewLeaf_ObjectStructure cleanup (Phase E) | Phase 1 prod cutover | Big-project plan for a unified intake-graph Apex service (`PatientOrderIntakeService`) called from BOTH a new Azure `@RestResource` AND a refactored data-entry screen flow. Phase 3 of the Azure roadmap + a deliberate consolidation of order-intake logic. Phases: A0 discovery (done — see `phase-a0-discovery.md`), A authoring, B screen-flow refactor, C REST endpoint, D per-channel cutover, E cleanup. **Three files: `plan.md` (canonical) + `phase-a0-discovery.md` (audit trail) + `visualization.html` (interactive companion).** A0 surfaced material §3 contract errors needing fix-up before Phase A. | | [`account-enhancement/`](account-enhancement/) | active (program — 2 children) | Kyle | 2026-05-09 | 2026-05-11 | — | Per-child blockers — see `account-enhancement/plan.md` | Umbrella program for Practice-Account data improvements requested by sales (Tyler Adcock 2026-05-08). Two children: (1) `elite-prescriber-rollup/` — DLRS Realtime count rollup of Elite Prescribers up to parent Practice (build-ready, pending Sarah review); (2) `practice-data-enrichment/` — one-time scrape of 1,245 Elite-flagged practice websites to find missing prescribers + secondary office locations. Python validator splits rows into auto-import vs human-review so most rows skip per-row review (draft, pending rollup ship + Sarah review). | | [`patient-portal-v2-release-qa.md`](patient-portal-v2-release-qa.md) | active (pre-deploy) | Kyle | 2026-05-10 | 2026-05-10 | — | Sarah's deploy of release into ClaudeTest + release narratives | Step-by-step QA runbook (checkbox format) for Marissa's Patient Portal V2 release (patient-facing portal for filling prescriptions) going live 2026-06-13/14. First manual execution of `multi-sandbox-kit.md` Phases 3 + 4 — snapshot ClaudeTest before + after Sarah's deploy, diff via `git diff`, two-pass review (conventions then intent), iterate. Manual stand-in for the not-yet-built `bin/snapshot-sandbox.sh` + `change-reviewer` agent. | | [`conversion-analytics-modernization/`](conversion-analytics-modernization/) | active | Kyle | 2026-05-11 | 2026-05-11 | — | Track B owner staffing decision + SFMC access restoration | Post-audit work plan for the Dec 2024 Brady/Measure Marketing Pro GA4 implementation. Three tracks: (A) Ownership rotation off departed consultant + urgent Google Ads connection disconnect (active data leak to Brady's agency account) — Kyle, ~3 hrs this week; (B) Conversion event buildout (dataLayer schema + ecommerce events + refill wizard events + 12 login funnel events + GA4 Key Events + server-side `purchase` from `convertCartToOrder`) — ~$7.5K–$10K at $150/hr; (C) Six storefront bugs surfaced during audit (wizard pricebook mismatch, wizard drops Rx attribution, profile-name-gated login lockout, charged-but-no-order hazard, cookie consent doesn't gate analytics, Order has no Refill_Reminder FK). Two files: `plan.md` (canonical) + `visualization.html` (stakeholder-facing). | ## Archived plans Closed (executed and complete) or superseded. Kept as institutional memory; do not delete. | Plan | Archived | Why closed | Successor / supersedes | | -------------------------------------------------------------------------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | [`archive/project-plan.md`](archive/project-plan.md) | 2026-04-19 | Original project plan (2026-04-16…2026-04-19) — discovery + distillation pass complete; per-object files written; CLAUDE.md + `.claude/rules/{apex,flow}.md` authored. | Superseded by `claude-after-dark.md` for the ongoing repo + automation track. | | [`archive/flow-knowledge-base.md`](archive/flow-knowledge-base.md) | 2026-04-26 | Three-layer flow knowledge base (indexes + per-flow summaries + workflow guides). Phases A + B + C-Pass-1.5 executed and shipped. | — | | [`archive/flow-summaries.md`](archive/flow-summaries.md) | 2026-04-26 | Per-flow Markdown summary generation plan; toolchain verified, 5-flow pilot run, executed for all 334 flows under `flows/_summaries/`. | Folded into `archive/flow-knowledge-base.md` as Phase B. | | [`archive/counter-proposal.md`](archive/counter-proposal.md) | 2026-04-26 | Phase 0 counter-proposal evaluated against the reference flow-KB plan; merged form is what was executed. | Merged into `archive/flow-knowledge-base.md`. | | [`archive/marissa-handoff-2026-04-19.md`](archive/marissa-handoff-2026-04-19.md) | 2026-04-28 | Original 2026-04-19 Marissa briefing. The 9 escalation items were migrated to GitHub Issues #6–#14 on 2026-04-28; `MARISSA-HANDOFF.md` at repo root is now a thin index pointing to those issues. The §3/§4/§6/§7 reference content is preserved here verbatim. | Live escalation status: GitHub Issues with the `escalation` label. | ## Adding a new plan 1. Name it `kebab-case.md` (single-file) or create `docs/plans//` (multi-file). No `PLAN-` / `PROJECT-` prefix. 2. Drop the file under `docs/plans/`, never at repo root, never directly under `docs/`. 3. Add a row to the **Active plans** table above. 4. Cross-link from CLAUDE.md or business-context/ only when the plan is load-bearing for code-touch decisions; otherwise the README inventory is the only required link. ## Closing or archiving a plan 1. `git mv docs/plans/.md docs/plans/archive/.md` (or the directory equivalent). 2. Move the row from **Active plans** to **Archived plans**, fill in the archive date and "why closed" + successor columns. 3. Update any in-repo cross-references that point at the live path. (Cross-references inside the archived file itself can stay — archived plans are frozen historical record.)