docs(demo): surface current IVR route-matrix proof

artifacts/demos/launchpad.extracted.md

@@ -19,10 +19,14 @@ Call flow is founder-demoed as phone -> Twilio -> VetCan voice AI -> inline rene
 Payment flow is founder-demoed as booking context first, then payment-safe options, PCI-safe capture path, SMS link fallback, unpaid follow-up, and dashboard visibility.
 Dashboard proof includes callback queues, exception handling, launch control, escalation health, and complete operator visibility.
 Why-this-works proof includes automated tests, rollback capability, uptime checks, alert escalation, and deployment visibility.
+Current IVR Route-Matrix Proof
+The current route proof is stronger and more specific than the original deck summary: Press 1 covers supported renewal, new-patient, and veteran callback conversion; Press 2 is annual Florida/MMU state-card help separate from seven-month doctor renewal; Press 3 uses deterministic after-hours classification, not live GPT/RAG; hidden Press 4 reschedule and cancellation request intake stay staff-confirmed by default; guarded payment capture belongs only to supported Press 1 booking/payment paths.
+Evidence should point to `ivr routing system.txt`, the focused route-boundary regression bundle, and CI-green route-boundary results.
 Boundaries
 This extracted markdown file is the current repo-local demo truth anchor; the checked-in binary path is not.
 Do not collapse founder-demo claims into live deployment authority.
 Do not treat demo slides about abandoned booking recovery or reactivation as proof of stronger runtime implementation than the repo actually contains.
+Do not describe Press 3 as live GPT/RAG, Press 4 as public self-service reschedule, cancellation as completed, veteran eligibility as guaranteed, or Acuity mutation as automatic where the runtime only creates staff-confirmed requests.
 Do not fold optional avatar/marketing platform ideas into the core VetCan operational proof or install-week packet.
 Derived From
 Uploaded founder-demo deck `launchpad.pptx`

docs/a22/A22_0_VETCAN_STUDIO_PREMIUM_DEMO.md

@@ -98,6 +98,18 @@ Current runtime-aligned demo proof for this surface:
 - public chat first-impression language stays cleaner and more operational on the current white-label path
 - monitor/improve and proof packaging stay consistent with these bounded runtime behaviors
 
+## Current IVR Route-Matrix Proof
+
+Owner-facing demo narration should now include the compact route-matrix proof from `ivr routing system.txt`:
+
+- Press 1 is the renewal / new-patient / veteran conversion lane. It can handle seven-month doctor renewals, new-patient scheduling, and the veteran callback script after full-pay and deposit decline.
+- Press 2 is annual Florida/MMU state-card help, separate from seven-month doctor renewal. It collects staff follow-up details and does not start payment capture or Acuity booking.
+- Press 3 is general questions and staff handoff during business hours, with deterministic after-hours classification only. Do not describe it as live GPT/RAG.
+- Press 4 remains hidden and staff-controlled for reschedule requests. Public self-service appointment movement stays off by default.
+- Cancellation is a separate staff-confirmed cancellation request, not a completed cancellation and not a reschedule unless the caller also asks to reschedule.
+- Payments stay guarded inside supported Press 1 booking/payment paths. General triage, Press 2, Press 3, reschedule, cancellation, and veteran callback intake do not collect payment.
+- Evidence is the current route matrix, focused route-boundary regression tests, and green CI for the route-boundary bundle.
+
 The deploy-readiness panel is explicitly blocked.
 
 Its live action remains disabled until external rollout approval and the separate

docs/a22/A22_7_PREVIEW_EVIDENCE_LEDGER.md

@@ -19,6 +19,7 @@ This ledger stays browser-local and does not activate any live clinic path.
 It supports internal review, preview comparison, and Studio packaging context only.
 It is not launch-week go-live proof and does not replace A18 cutover evidence, acceptance export, or rollback verification.
 It also does not replace supervised practice-booking proof against the live Acuity pool.
+Route-matrix proof should stay anchored to `ivr routing system.txt` and the focused route-boundary regression bundle, not inferred from preview-ledger entries alone.
 
 ## Storage Contract
 
@@ -67,6 +68,14 @@ The Preview & Test Center now shows:
 
 The main Studio shell consumes the stored ledger when rebuilding the improve loop and export package.
 
+## Route-Matrix Evidence Boundary
+
+When A22 demo packaging references current IVR proof, pair preview evidence with the implementation-truth route matrix:
+
+- Press 1 booking/payment and veteran callback conversion evidence belongs to the supported booking lane.
+- Press 2 state-card separation, Press 3 deterministic after-hours routing, hidden staff-controlled reschedule, and separate cancellation request handling are route-boundary proof, not preview-ledger proof by themselves.
+- The ledger may support rehearsal context, but route-boundary tests and CI-green results are the proof for the current IVR route matrix.
+
 ## Verification
 
 Focused verification for A22.7:

docs/a22/A22_8_APPROVAL_PUBLISH_PACKAGE.md

@@ -69,6 +69,7 @@ Package contents:
 - approved brief snapshot
 - approved persona, current draft controls, and selected workspace preview mode
 - preview evidence summary
+- route-matrix proof pointer for Press 1 / Press 2 / Press 3 / hidden Press 4 / cancellation boundaries
 - humanization summary
 - readiness decision
 - blocker list
@@ -106,9 +107,16 @@ This keeps Studio honest about:
 
 - preview-only posture
 - routing truth
+- staff-controlled reschedule and cancellation posture
 - rollout manifest authority
 - live deployment remaining blocked
 
+Current route-matrix language in the package should stay bounded:
+- Press 3 after-hours classification is deterministic, not live GPT/RAG.
+- Hidden Press 4 captures staff-confirmed reschedule requests by default; it does not advertise public self-service movement.
+- Cancellation intake creates a staff-confirmed request and does not complete or mutate the appointment automatically.
+- Payment capture is guarded to supported Press 1 booking/payment paths and is not generalized to triage.
+
 Install-week gate reminder:
 - read `docs/delivery/DELIVERY_TRUTH_FREEZE.md` before using this package in install-week review
 - use `docs/delivery/OUTBOUND_LIFECYCLE_LANE.md` and `docs/delivery/OUTBOUND_CAMPAIGN_CATALOG.md` before treating outbound/reminder/reactivation wording as current delivery wording

docs/a22/A22_9_DEMO_LAUNCHER.md

@@ -57,6 +57,14 @@ Clinic-launcher proof language should stay aligned with current shipped behavior
 - cleaner public-chat first-impression wording is treated as current surface truth, not future polish
 - operator proof remains anchored to Preview evidence, Dashboard proof, and blocker-honest launch control
 
+Strongest clinic demo scenarios:
+
+- Press 1 renewal / new-patient / veteran conversion: show inline booking strength, guarded payment capture only where supported, and veteran callback intake without promising eligibility or event availability.
+- Press 2 state-card separation: show that annual Florida/MMU state-card help does not get confused with the seven-month doctor recommendation renewal.
+- Press 3 after-hours classification: show deterministic routing for renewal, state-card, new-patient, veteran, medical, callback, reschedule, and cancellation intents without claiming live GPT/RAG.
+- Hidden reschedule and cancellation posture: show that reschedule and cancellation requests are captured for staff confirmation, with Press 4 hidden from the public menu and no default public Acuity mutation.
+- Route-boundary proof: pair the scenario with `ivr routing system.txt`, the focused route-boundary regression bundle, and CI-green evidence.
+
 Install-room boundary for this launcher:
 - founder/demo narrative stays separate from install-room proof
 - this launcher may support rehearsal and presentation context, but it does not satisfy the canonical install-room proof order