docs(caring-contacts): land the rollout plan, design-phase plan and coordination spec - #2133
Conversation
…oordination spec The Caring Contact prototype merged as #2095, but the reasoning that produced it stayed in an uncommitted local worktree with no remote branch — roughly 1,550 lines that existed nowhere else and would have vanished with that directory. - 2026-08-14 rollout plan (1,054 lines): the repository-native rollout, staged from approved visual and clinical-operating model through synthetic-data build, governed integration, limited pilot and measured expansion. It records the decisions that constrain the prototype — dedicated route group rather than a searchable Clinical KB mode, no patient data through the RAG/OpenAI path, and an explicitly approved PHI-capable identity, hosting, datastore, audit and SMS boundary required before any real-patient use. - 2026-08-15 design-phase plan (311 lines). - 2026-08-15 coordination design spec (185 lines): the binding synthetic-design specification, tied to the design-system SPEC/TOKENS/COMPONENTS/GATES. Documents only. The eleven superseded design-phase screen modules from the same worktree are archived on codex/caring-contact-design-20260815 rather than landed here, since they were reorganised into the merged prototype and would otherwise add unreachable modules that the dead-code gates reject. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in:1 minute Limit details: You’ve used all 1 included review currently available under your plan. You completed 101 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour. Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
Comment |
This pull request has been ignored for the connected project Preview Branches by Supabase. |
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
Lands the planning trail behind the Caring Contact prototype. The prototype itself merged as #2095; the reasoning that produced it was still sitting uncommitted in a local worktree with no remote branch, roughly 1,550 lines that existed nowhere else and would have gone with that directory.
2026-08-14-caring-contact-coordination-rollout.md(1,054 lines) — the repository-native rollout, staged from an approved visual and clinical-operating model through a controlled synthetic-data build, governed integration, limited pilot and measured expansion. This is the document that constrains the prototype: a dedicated route group rather than a searchable Clinical KB mode, no patient data through the existing RAG/OpenAI path, and an explicitly approved PHI-capable identity, hosting, datastore, audit, records and SMS boundary required before any real-patient use.2026-08-15-caring-contact-design-phase.md(311 lines) — the design phase plan.2026-08-15-caring-contact-coordination-design.md(185 lines) — the binding synthetic-design specification, tied to the design-systemSPEC/TOKENS/COMPONENTS/GATES.Documents only. No code, no routes, no configuration.
What was deliberately not landed
The same worktree held eleven superseded design-phase screen modules — today, schedule, patient agreement, patient overview, pathway selection, patient boundary, delivery exception, template, team/guidance/reporting, a continuity-thread specimen and mockup primitives. The merged prototype reorganised those into
product-pages/routable-suite/activation-workflow, so committing them here would add unreachable modules that this repository's dead-code gates reject. They are preserved on the archive branchcodex/caring-contact-design-20260815instead, which now exists on the remote for the first time.Verification
npm run docs:check-links—docs link check passed: 1901 repo path references resolve(the spec cross-links four design-system documents, so this is the check that matters).npm run format— clean.Not run, with reason: lint, typecheck, the unit suite and browser gates. The diff is three Markdown files under
docs/superpowers/; none of those gates has a failure path here.Risk and rollout
Notes