Skip to content

Planning Documents

This directory contains planning and strategy documents for CareConnect.

Historical note: files under docs/planning/archive/ preserve earlier phases of the project and may still use pre-CareConnect naming or transitional branding. Treat those references as historical only; current operational guidance uses the CareConnect name and careconnect.ing.

Active Planning: v22.0

Status: v22 Gate 0 remains NO-GO pending C1/D4 closure. Service reverification is the parallel safety priority. The approved eight-record Brampton first launch is complete; future verification, expansion, and official/partner wording remain approval-gated rather than an active launch track. Created: 2026-02-27

Quick Start (Read These First)

  1. Roadmap ⭐ START HERE
  2. Executive status, ordered priorities, stop rules, active decision work, and deferred tracks

  3. Reading time: 7 minutes

  4. v22.0 Non-Duplicate Value Decision Plan

  5. Strategic objective, hypotheses, kill rules, and stage gates

  6. Reading time: 15 minutes

  7. Brampton Launch Readiness Report

  8. Current Brampton launch evidence, completed production/QA status, and remaining verification/approval gates
  9. Reading time: 10 minutes

Detailed Documentation (Optional)

Document Navigation

docs/planning/
├── README.md ← You are here
├── roadmap.md (main roadmap, updated for v22.0 and Brampton)
├── archive/ (completed version plans)
├── archive/2026-06-04-public-github-cleanup.md
├── archive/2026-05-01-v20-0-public-and-operational-surface-polish.md
├── archive/2026-04-30-v20-0-about-page-polish.md
├── archive/2026-04-29-v20-0-homepage-search-ux-polish.md
├── archive/2026-04-28-v22-0-gate-0-prep-and-deploy-contract-alignment.md
├── archive/2026-04-24-v20-0-repo-audit-truth-remediation.md
├── archive/2026-04-23-v20-0-quiet-github-automation-and-url-health-hardening.md
├── v21-external-validation-plan.md
├── archive/2026-04-15-v20-0-semantic-search-fail-closed-and-lint-hygiene.md
├── archive/2026-04-01-v22-0-pilot-metric-instrumentation-and-tier-0-hardening.md
├── v22-0-non-duplicate-value-decision-plan.md
├── v22-0-approval-checklist.md
├── archive/2026-04-01-v20-0-workflow-runtime-cleanup-and-211-sync-quarantine.md
├── archive/2026-06-28-autonomous-maintenance-plan.md
├── archive/2026-06-28-autonomous-maintenance-status.md
├── archive/2026-03-18-careconnect-rebrand.md
├── archive/2026-03-30-v20-0-runtime-hardening-and-performance-remediation.md
└── archive/2026-03-29-v20-0-repo-audit-remediation.md

Quick Reference

What is active now?

One strategic track is active: v22.0 Non-Duplicate Value Decision Plan. It tests whether CareConnect provides measurable last-mile value relative to 211 while preserving explicit privacy and stop rules.

Three human-owned lanes run in parallel:

  1. Reverify services, starting with the 42 stale Crisis records.
  2. Supply the missing C1 legal/API terms evidence.
  3. Supply the missing D4 partner-operations execution evidence.

Brampton's approved eight-record launch is complete. Further candidates or L2/L3 changes are gated follow-up work, not a second active roadmap track.

Why Now?

The platform is technically mature, but the next decision is strategic rather than purely technical:

  • Avoid direct breadth competition with 211
  • Validate measurable last-mile outcome value
  • Keep governance and privacy redlines explicit before expanding pilot work

Timeline

Target ~90-day decision review cycle

  • Phase 0: baseline + governance locks
  • Phase 1: pilot execution
  • Phase 2: objective go / conditional / stop decision

This is a decision checkpoint target, not a guaranteed delivery schedule. The review window assumes external blockers such as legal review and partner evidence close in time to support a meaningful decision.

Cost

Pilot cost remains bounded by existing infrastructure and partner participation assumptions documented in the v22 plan.

Dependencies

Current dependencies and completed prerequisites:

  • Gate 0 blocker closure (C1, D4)
  • Baseline evidence already published
  • Integration feasibility decision already recorded in conditional mode
  • Offline F3 replay and F5 bounded recovery evidence recorded; F1 queue inspection and F2 authenticated sign-out QA remain evidence-gated
  • Brampton first-launch production, accessibility, visual QA, and broad-coverage closeout already recorded

How to Proceed

Option 1: Reverify Services

Use the dated freshness worksheet and the open verification issues:

  1. Start with the 42 stale Crisis records in issue #13.
  2. Continue the general quarterly queue in issue #14.
  3. Update facts and provenance.verified_at only after real phone/web/source evidence is recorded.
  4. Regenerate the freshness audit after each reviewable verification batch.

Option 2: Close Gate 0

Use the active roadmap and Gate 0 tracker to close the remaining v22 blocking items:

  1. Attach candidate partner legal/API terms for C1 review
  2. Attach named pilot partner and outreach execution evidence for D4

Option 3: Continue a Specifically Approved Brampton Record

Use the Brampton verification workplan only after a candidate or L2/L3 change is explicitly approved. Do not treat the completed first launch as permission for broad regional expansion.

Document Updates

  • 2026-07-13: Reorganized the roadmap around one active strategic track, a P0 service/legal/partner evidence stack, explicit completion conditions, and concise maintenance/deferral rules; moved Brampton to a completed bounded-launch track and corrected F1/F2 threat-model status
  • 2026-03-24: Planning index updated to reflect Gate 0 NO-GO blockers and current close-out order
  • 2026-03-29: Planning index updated to reflect completed C2 closure and remaining C1/D4 blockers
  • 2026-03-29: Added v20.0 repo-audit remediation archive and removed the stale reference to a nonexistent active v20 migration-recovery plan
  • 2026-03-30: Added the v20.0 runtime hardening and performance remediation archive and refreshed roadmap baseline metrics after the audit-driven maintenance wave
  • 2026-04-01: Added the v20.0 workflow runtime cleanup and 211 sync quarantine archive after closing the remaining Node-runtime workflow follow-up
  • 2026-04-01: Added the v22.0 Tier 0 external-validation support archive and updated the roadmap to treat pilot metric, public-claim, and focused privacy test hardening as complete baseline capability
  • 2026-04-01: Added the re-triaged v21 external-validation plan to the planning index and aligned the main roadmap with the new tiered sequencing
  • 2026-04-03: Finalized the CareConnect rebrand archive after the GitHub repo rename to jerdaw/careconnect
  • 2026-04-15: Added the semantic-search fail-closed and lint-hygiene archive after restoring actionable repo-wide linting and hardening the embedding-worker fallback path
  • 2026-04-23: Added the quiet GitHub automation and URL-health hardening archive after converting recurring governance workflows to quiet-by-default issue reuse and stabilizing the monthly health check against CI-only false positives
  • 2026-04-24: Archived the repo audit follow-up/remediation wave after the direct-VPS docs/privacy/planning reconciliation pass completed
  • 2026-04-28: Archived the Gate 0 prep and deploy-contract alignment pass after adding prep-only C1/D4 evidence packets, syncing tracker wording, and validating the sudo-required shared frontend env-file contract
  • 2026-04-29: Archived the homepage search UX polish pass after moving filters into the active search/results state, restoring and refining the service/category/language metrics rail, folding trust-strip content into the How It Works flow, and validating spacing/contrast updates
  • 2026-04-30: Archived the About page polish pass after consolidating trust/context content, restoring the smooth page-level background, aligning sections on a shared rail, and validating CTA styling updates
  • 2026-05-03: Refreshed roadmap baselines from current local validation, corrected the production/full dependency audit status, and added bounded dependency-audit remediation to active maintenance
  • 2026-06-04: Added the public GitHub cleanup archive after establishing ADR-022 and sanitizing public deployment, operations, planning, legal, and observability documentation
  • 2026-07-05: Added the maintenance audit checkpoint and refreshed roadmap test, coverage, and dependency-audit baselines after the repo-health pass
  • 2026-07-07: Updated the active roadmap for the Brampton constrained multi-city launch track, refreshed 203-record data-quality counts, linked launch readiness docs, and reordered next work around a11y/browser QA, completed authenticated schema preflight, and approval gates
  • 2026-03-24: v20.0 DB integration test lane archived; migration-history cleanup remains on the active roadmap
  • 2026-03-18: Planning index updated for v22.0 and CareConnect rebrand archive
  • 2026-03-18: CareConnect rebrand archived in docs/planning/archive/2026-03-18-careconnect-rebrand.md
  • Next review: After any UA-1 / UA-2 / UA-3 evidence update or the next material roadmap change