3.7 KiB
Phase 9 — Form A owner acceptance record
Recorded: 2026-10-28 UTC
Scope: Form A (262946078314059) only
Evidence type: owner-reported Jotform and browser acceptance; not independently reproduced by this repository task.
Accepted functional scope
The owner reports that Form A is approved for production use subject to the separate Astro production gate and site-release process. The owner reports successful direct-Jotform synthetic submissions in English and Spanish, native confirmation behavior, notification and autoresponder delivery, and deletion of the test submissions.
The owner also reports successful synthetic submission and confirmation through the isolated Astro iframe at:
/contact(English contact)/es/contact(Spanish contact)- one ABA landing placement
The owner report calls the third route an ABA landing page but does not name its exact path. This record deliberately does not infer a route from the four-route ABA landing allowlist. Record that path in the release test log before declaring all seven placements submission-tested.
These reported tests complete Form A functional submission acceptance for the sampled direct and embedded journeys. They do not independently prove that every allowed page placement has passed a full submission flow.
Automated repository evidence
The repository's guarded test suite renders all seven allowlisted placements with fixed URLs and contexts:
| Route | Locale | Context | Submission evidence |
|---|---|---|---|
/contact |
EN | contact |
Owner-reported embedded synthetic sample |
/es/contact |
ES | contact |
Owner-reported embedded synthetic sample |
/lp/aba-therapy |
EN | landing |
Automated rendering; may be the reported ABA sample only after route confirmation |
/lp/aba-insurance |
EN | landing |
Automated rendering only |
/lp/aba-ahcccs |
EN | landing |
Automated rendering only |
/lp/aba-private-pay |
EN | landing |
Automated rendering only |
/lp/early-intervention |
EN | landing |
Automated rendering only |
The automated checks do not submit data, inspect the cross-origin frame, infer conversion from load, or transmit Jotform, API, analytics or advertising requests.
Embed-handler decision
The official Jotform resize/embed handler is conditionally acceptable pending targeted verification. It is not part of the current fixed-height adapter. Before any adoption, a separately authorized review must inspect its current source and dependencies, message-origin and source-window checks, URL mutation, parent-page privileges, network requests, sandbox interaction, Firefox behavior, validation/error expansion and failure states. No change to the fixed-height implementation is authorized by this decision record.
Still required before a site release
- The exact submitted ABA landing route must be recorded.
- All seven placements need final responsive, keyboard, screen-reader, error-state and fluent-language acceptance.
- Privacy/security owners must review Jotform runtime requests and telemetry, embed/referrer behavior and deployment configuration.
- Hosting owners must accept the HTTPS host, CSP/referrer/log policy and production environment gate.
- Marketing notification routing remains a pre-cutover operational check; it is not changed by this record.
- Form A
consultationremains unconfigured and unverified; physical Form B is retired; Form C remains unimplemented and unverified. - Phase 10 requires a separate release-owner go/no-go and rollback rehearsal.
No Jotform account settings, recipient routing, submissions, analytics, advertising, API behavior, hosting configuration or deployment was changed while recording this evidence.