docs(forms): adopt two-form consultation architecture
This commit is contained in:
10 files changed
+198
-89
No files matched your search
@@ -20,6 +20,10 @@ The owner supplied this revised decision: use Form A (`262946078314059`) for the
|
||||
|
||||
The 2026-10-26 owner decision supersedes the earlier exception for `/lp/early-intervention`. Its existing AIA-branded card keeps its off-mode controls and shows the embedded Form A adapter only when the same isolated-test gate permits it. There are no Spanish campaign routes in this implementation, so no Spanish landing parameter has been invented.
|
||||
|
||||
## Supersession addendum — 2026-10-28
|
||||
|
||||
The earlier statement that Form B remained the destination for other service-consultation journeys is superseded. Physical Form B is retired. Those journeys are now future Form A `consultation` targets, subject to the separate Builder, clinical, privacy, synthetic-acceptance and Astro-allowlist work in [the two-form integration specification](phase-9-two-form-integration-specification-2026-10-28.md). This addendum does not change the five current landing placements, their fixed `landing` context or the seven-route gate.
|
||||
|
||||
## Implementation
|
||||
|
||||
`src/utils/form-integration.ts` now owns one typed route/locale/context allowlist for all seven Form A placements. `resolveFormAIframe` still requires every existing isolated-test gate:
|
||||
|
||||
Reference in new issue
Block a user