Skip to content

CareConnect: Product Roadmap

Current decision: controlled public-service retirement completed

Execution status: evidence screen closed; frontend retirement deployed and verified on 2026-08-15

Public state: localized non-service retirement surface; no actionable CareConnect directory

Active product work: none

Stewardship: exception-only and automated by default; no recurring human maintenance cadence

Executive Status

Area Current state Authority or evidence
Strategic disposition The actionable public directory was retired on 2026-08-15 after the bounded screen did not corroborate meaningful recurring human benefit or identify an accountable steward Retirement disposition
Service inventory The governed snapshot contains 204 records; the dated 2026-08-12 freshness check identifies 8 visible records and 196 stale/hidden records Reproducible local staleness check; no service record was changed
Crisis stewardship The frontend retirement exposes no service records. The two records that were due at the 2026-08-12 snapshot remain unchanged in the underlying inventory; any record change is a separate approval-gated action Existing freshness policy and dated staleness check
Use evidence CC-2B was closed without a query because the allowed aggregate contract could not establish people, referrals, outcomes, or public benefit; 116 screen minutes remain unused Retirement disposition
Frontend retirement The localized retirement surface was deployed from main revision ef91ac67c8a7 on 2026-08-15 and passed the public and browser acceptance contract. Service data, Supabase, workflows, shared keepalive, and DNS were unchanged Transition and rollback packet
Shared operations The unchanged Actions workflow queries both CareConnect and VisitBrief Supabase Data APIs directly and is independent of the CareConnect frontend. Its latest checked scheduled run on 2026-08-15 succeeded. Keep the workflow, repository, Actions, required secrets, and Supabase projects intact Public keepalive workflow contract plus private/shared operations source of truth
Recovery boundary Live release, backup, rollback, shared-host, and environment details remain outside this public repository ADR-022

Ordered Work

CC-1 — Documentation truth

Completed. Canonical public status, navigation, roadmap, and the decision record distinguish the closed evidence screen, the deployed frontend retirement, and the unchanged data/shared-service boundary.

CC-2 — Bounded evidence screen

Closed after CC-2A used 4 of 120 minutes. CC-2B was not pursued because the available browser session was unauthenticated and the allowed aggregate endpoint contract could not establish people, referrals, outcomes, or benefit. Production SQL, raw logs, personal data, and credential extraction remained out of scope. The unused 116 minutes do not carry into a broader search.

The screen could have established activity consistent with recurring human use, but aggregate requests alone would not have proved unique users, referrals, outcomes, or benefit. No qualifying evidence or accountable steward was documented; the screen closed and did not carry forward into another evidence campaign.

CC-3 — Reversible artifact preservation

Completed: source/history, a dated public visual baseline with hashes, and a reproducible retirement release remain preserved. No real actionable listing is retained as a public demo solely for optionality.

CC-4 — Approval-gated transition

Completed on 2026-08-15 after the recovery and cross-project dependency preflights passed and the owner approved the bounded database-recovery risk and exact live action. The deployed main revision is ef91ac67c8a7. Service-record changes, Supabase changes, workflow or shared-keepalive changes, redirects, and future deployments remain distinct approval gates.

Exception-Only Post-Retirement Stewardship

CareConnect has no standing maintenance, validation, or evidence campaign. Existing automation is the default for preserving retirement status and required infrastructure. Human work begins only when a material public-truth change, an automated safety/status/security signal, or a rollback, infrastructure, or data-loss risk requires a bounded response.

Permitted responses are limited to:

  1. Correcting canonical public retirement status when it becomes materially inaccurate.
  2. Preserving or recovering verified rollback and required infrastructure artifacts within their existing approval boundaries.
  3. Containing a genuine safety, status, security, or data-loss incident within separately approved scope.
  4. Running only the change-triggered or incident-triggered public GET checks and local validation needed to verify that response.

Do not create a periodic manual check, documentation-hygiene, content-refresh, or validation cadence for optional assurance.

Blocked by Default

  • Corpus restoration, optionality reverification, data expansion, and regional expansion.
  • Product-led outreach, partner pitches, pilot execution, research conversion, and new evaluation instrumentation.
  • Production SQL, credential extraction, raw-log or personal-data access, and live Supabase or schema changes.
  • Changes to crisis records, GitHub workflows, VisitBrief keepalive coverage, shared infrastructure, redirects, or deployments.

Reopening Gate

Service implementation or evaluation may reopen only when all of the following are present:

  1. An independently supported service need.
  2. An accountable operational steward that owns record freshness.
  3. Institutional ownership of governance, privacy, safety, and any required ethics or QI pathway.
  4. A bounded evaluation or implementation decision with explicit success and stop criteria.
  5. Evidence that the proposed service is preferable to 211, a simple process or spreadsheet, or doing nothing.

A problem-first needs assessment does not require the public directory to remain online and does not by itself reopen implementation.

Historical Authority

The July 2026 limited-public-directory disposition and the v19-v22 pilot, launch, and external-validation plans are superseded as active authority. They remain in the repository as historical evidence; their checklists and queues do not authorize current execution.

Documentation-Platform Boundary

CareConnect remains on the current MkDocs 1.x/Material stack. Do not start a documentation-platform migration while the post-retirement disposition remains in force; any shared migration wave requires separate cross-project approval.

Historical Anchor Compatibility

The headings below preserve links from completed technical records. Their work is historical and does not reopen an active roadmap lane.

v20.0: Technical Excellence & Testing (High Priority - Before Production)

Superseded by the current retirement disposition. See the v20 autonomous backlog closeout for the completed historical record.

Category B: Test Coverage (60h) — Largest Gap

Superseded as an active estimate. Current validation is limited to checks required for an approved exception response or preservation action.