Project overview

Status: Proxi-controlled Cloudflare operating manual, eight-pillar sequence atlas, and review inbox published; owner adjudication of workforce and SOP semantics is in progress
Last updated: 2026-07-15

This directory is the source of truth for defining the work ProxI-enabled CMS GUIDE services must actually perform. The current public-source inventory contains 359 tasks across the eight GUIDE service domains in scope, 138 GUIDE program-operation tasks outside those services, and 106 evidence-backed candidate tasks above the public GUIDE minimum: 603 classified tasks overall. Each body of work identifies what the task entails, what Proxi could potentially automate, who is required, whether the task is a GUIDE requirement or other necessary work, the customer-value position, and whether clinical judgment is actually required.

Current-phase guardrail#

Work on the business service semantics first. Expand the literal procedure, required result, source facts, preparation work, automation opportunity, human judgment, minutes, failure handling, and completion evidence before building software scaffolding. Do not add versions, hashes, machine schemas, state machines, fault gates, or automation implementation during this phase. Review one service procedure at a time and correct the actual work, candidate Proxi contribution, and human responsibility.

Governing premise#

Probabilistic systems may observe, extract, transform, summarize, and speak. They do not decide. Versioned deterministic rules govern workflow, routing, permissions, state transitions, escalation, and closure. Licensed humans exercise clinical judgment where required. Deterministic executors act only after every required fact and authorization is present.

Document map#

Current continuation checkpoint#

The stable current-work pointer is the newest append-only record in reviews/checkpoints/CURRENT.md. It records the active Codex task, newest controlling user instruction, last completed artifact checkpoints, and exact bounded continuation. Append a START, PAUSE, or DONE record at the corresponding boundary; do not rely on the sidebar as the sole continuation record.

The last completed artifact checkpoint is reviews/checkpoints/real-role-normalization-2026-07-15.md. The preferred reading and owner-review surface is the Proxi-controlled Cloudflare website at https://guide.proxi.care, generated from website/; it has no ChatGPT or Claude authentication layer. The current normalized-role correction is verified locally but intentionally not deployed yet, so the live site remains the prior revision until owner review. The site presents 28 mapped project documents, gives all eight service SOPs equal task-level visibility across 359 source-bound tasks, and adds a clickable sequence atlas with nested authority, handoff, accounting, and worked-episode views. Each diagram step, named section, and task row links back to its controlling source and can be flagged or commented on. The structured Review Inbox at /review preserves canonical source excerpts in the dedicated Proxi Cloudflare D1 database for later LLM-assisted adjudication.

The last completed semantic checkpoint is reviews/checkpoints/eight-pillar-service-integration.md. All eight service SOPs now participate in one source-preserving service loop: Comprehensive Assessment establishes the initial, annual, or bounded current baseline; Care Plan carries beneficiary-led actions; Ongoing Monitoring and Support follows results and returns material changes; and 24/7 Access, Care Coordination, Medication Management, Referral/Services, and Caregiver Education/Support open and return their own distinct work. D-021 still controls preparation before judgment, and D-016 still counts shared human work once while requiring separate service content and results. Program Operations remains supporting infrastructure, not a ninth care pillar. Formal actor, timing, release, service-evidence, workload, and Participant-specific validation remains open in the linked decision log. Do not begin Fault Gate 2, Fault Gate 17, machine representation, or automation implementation until the semantic procedures are accepted.

The prior portfolio workforce baseline remains at reviews/checkpoints/guide-human-workload-estimates.md. The detailed cards now expose role-specific minutes across every service, but the portfolio totals remain provisional until the service-level event assumptions, incidence, shared-interaction accounting, and low/typical/high rollups are owner-validated. The commercial scope remains settled: Proxi maintains, staffs, and furnishes all eight GUIDE service domains in scope as applicable to each beneficiary's and caregiver's needs, and respite alone is excluded. This is full-package capability and ownership, not a requirement that every beneficiary receive every domain every month.

Working method#

1. Break each GUIDE service obligation into the actual tasks needed to deliver it.
2. Describe what each task entails instead of restating the service heading.
3. Identify the concrete part Proxi could potentially perform or accelerate.
4. Separate Proxi-paid work from beneficiary, caregiver, participant-customer, clinician, and external-party actions before discussing staffing or cost.
5. State whether a person is required, name the actual role, and state whether Proxi or the customer would supply that role under the proposed service offer.
6. Separately state the GUIDE standing, customer-value position, and clinical lane; never use “human required” as a synonym for “clinical judgment required.”
7. Keep distinct beneficiary, caregiver, clinical-provider, transition, and community-service routes separate.
8. Review and correct one service table at a time until the business work is accepted.
9. Only after semantic acceptance, apply Fault Gate 2 and then Fault Gate 17.
10. Leave implementation mechanics until after those reviews.

Current scope#

This working set covers eight GUIDE service domains:

• Comprehensive assessment
• Person-centered care plan
• Ongoing monitoring and support
• 24/7 access
• Care coordination and transitional care management
• Referral and coordination of services and supports
• Medication management and reconciliation
• Caregiver education and support

Respite is intentionally excluded from this operating scope.

Status notation#

• SETTLED: Governing assumption; do not change without a decision-log entry.
• PROVISIONAL: Working design requiring operational, clinical, contractual, or legal validation.
• OPEN: Unresolved decision with an assigned owner.
• BLOCKED: Cannot proceed until a named dependency is resolved.