Skip to content

Planning Documents

CareConnect's controlled public-service retirement is complete. The bounded evidence screen is closed, and the localized non-service retirement surface was deployed and verified on 2026-08-15. The actionable public directory is no longer available.

Post-retirement stewardship is exception-only and automated by default. There is no recurring human maintenance, validation, or evidence cadence.

Start Here

  1. Current Roadmap — active priorities, gates, and stop rules.
  2. Public-Service Retirement Disposition — owner decision, evidence boundary, and reopening requirements.
  3. Retirement Transition and Rollback Packet — public-safe live preflight, acceptance, rollback, and evidence contract.

These documents are the current planning authority. Detailed v19-v22 plans, checklists, and implementation records remain useful historical evidence, but they no longer authorize pilot execution, corpus reverification, partner outreach, expansion, or feature work.

Completed Retirement Work

Order Work Boundary Completion condition
CC-1 Reconcile canonical public documentation Completed; canonical navigation and status surfaces record the deployed retirement Canonical navigation and status surfaces agree
CC-2 Close the bounded evidence screen Closed at 4 of 120 minutes; CC-2B not pursued; no new tracking, SQL, raw logs, or credentials The disposition records why allowed evidence cannot satisfy the continuation gate
CC-3 Preserve a reproducible non-service artifact Completed; source/history, dated visual baseline, and signed release evidence retained Code/history, hashes, screenshots, and local validation are recoverable
CC-4 Execute the selected public transition Completed on 2026-08-15 after recovery/dependency preflight and explicit live approval Public state matches the approved disposition and rollback evidence is preserved

Stop Rules

  1. Do not restore or reverify the corpus for optionality.
  2. Do not start a pilot, partner pitch, housing workflow, research conversion, feature expansion, or new instrumentation.
  3. Do not treat aggregate traffic as proof of unique people, referrals, outcomes, or public benefit.
  4. Do not alter crisis records, Supabase, shared keepalive behavior, workflows, or the public deployment without the applicable explicit approval and recovery preflight.
  5. Keep public rationale limited to project stewardship, safety, evidence, and operations; retain private operations details in their existing source of truth.

Historical Plans

The following documents are retained for traceability and are not active execution authority:

Historical note: archived documents may use earlier project names or describe work that was valid in an earlier phase. Current guidance uses the CareConnect name and the disposition linked above.