docs(referrals): retire Form C plan and document existing hosted workflow

This commit is contained in:
DeCentN2Madness committed 2026-11-01 18:10:54 -07:00
1 parent 5c8ba2e11e
commit 80e0c405bc
9 files changed
+141 -30

No files matched your search

@@ -1,5 +1,12 @@
# Phase 9 — Decision register
> **2026-11-01 referral decision:** The `/referrals` CTA now uses the existing
> hosted Jotform at https://form.jotform.com/231638510219149. Do not create Form C.
> P9-03 remains open for review of that legacy destination's actual privacy,
> notification/recipient, clinical and operational configuration. Older Form C
> references below are historical and superseded.
>
Recorded: 2026-10-14 (source review began October 13). Prepared during Phase 7; no decision or integration is approved by this register. Owner roles are proposed responsibilities, not assigned individuals. Every item is **Pending decision**. A technical option is not approval; translation is not legal/clinical sign-off; browser acceptance is not deployment authorization.
## P9-01 — Landing-page ownership
@@ -35,14 +42,14 @@ Recorded: 2026-10-14 (source review began October 13). Prepared during Phase 7;
## P9-03 — Form/API ownership
- **Status:** Pending decision
- **Current implementation:** Form A has seven production-eligible placements and nine separately gated, isolated-test-only consultation placements; all other shared form controls remain disabled with no backend. Physical Form B is retired; Form C remains future work. The consultation surfaces are not production-authorized.
- **Current implementation (superseding 2026-11-01 decision):** Form A is live by default at its fixed 16 placements. `/referrals` renders a button linking to the existing hosted Jotform (https://form.jotform.com/231638510219149) without an inline form; the Form C plan is canceled.
- **Evidence:** [two-form integration specification](phase-9-two-form-integration-specification-2026-10-28.md), [../src/components/FormShell.astro](../src/components/FormShell.astro)
- **Options:** Approved direct Jotform Form A consultation and separate Form C; no Contabo backend for protected lead data.
- **Current direction:** Retain Form A for its 16 approved routes and the existing externally hosted Jotform for `/referrals`; no Form C creation or Contabo lead-form backend.
- **Risk if unresolved:** Lost inquiries, accidental collection, unsafe retention or ambiguous failure.
- **Decision owner role:** AIA intake/operations owner
- **Required reviewers:** Privacy/legal/security
- **Dependencies:** Field necessity, recipient, spam controls, retention/access, failure handling, P9-07/09
- **Acceptance criteria:** Synthetic nonproduction submission success/failure, no-JS/Enter behavior, access and retention documented; explicit activation approval.
- **Acceptance criteria:** Verify current referral button URL, hosted form accessibility, actual submission/recipient paths, clinical/privacy controls, retention, failure handling and continued availability; record production release decision.
- **Impacted routes/systems:** Contact, consultation, referrals, service drawer
- **Authorization required:** Explicit owner decision, then a bounded implementation/test scope; live activation/deployment requires separate authorization.
- **Resolution date/evidence:** None; not approved.