The live form is visible for review, but website delivery is not connected.

• Intent changes the message prompt and preserves whether the visitor wants to discuss, challenge, or suggest.
• Operating layer preserves whether the situation concerns records, field decisions, both, or is not yet clear.
• Message demonstrates required-description handling and can be placed into a user-controlled email draft.
• Work email exercises required-email validation in private testing and can provide a reply address in an email the visitor chooses to send.
• Name and organization are optional identifiers for that user-controlled draft and for synthetic layout testing.
• Phone or video preference is optional and does not promise a meeting.
• Source route, form version, and generated test ID make a synthetic QA receipt traceable to the tested route and contract.
• The hidden website field exercises a synthetic spam-filter response; it is not a verified production abuse control.

Do not enter customer facts, credentials, regulated data, sensitive personal information, confidential information, or controlled records.

The public review page disables form submission in the browser and shows that delivery is not connected. The server independently rejects POST requests received on the production hostname before it parses a submitted body.

Typed values remain in browser component memory until the visitor navigates away or reloads. The application does not write them to a database, CRM, email service, file, cookie, local storage, or session storage.

The private/local test form sends JSON to /api/staging-contact, requires a reserved email ending in .example, validates the payload, and returns deterministic receipt or error states.

The application code does not store or forward those values. A successful response is an ephemeral synthetic receipt—not a real inquiry, notification, assignment, CRM record, spam-control result, or delivery confirmation.

The email restriction cannot determine whether free-text fields are synthetic. Reviewers must use invented values and follow the warning above.

The fallback builds a draft addressed to Signal Trapper with the current intent, layer, source, and typed values. Nothing is sent until the visitor reviews and sends that draft from an email application.

After it is sent, the visitor's and recipient's email providers process the message. Current mailbox ownership, access, routing, security, retention, deletion, and reply handling have not been verified for a complete production notice.

OpenAI Sites hosts the website. The separate private staging project was verified as owner-only on 2026-08-23; the public production project is intentionally public.

The synthetic staging payload declares processing purpose as form verification, reply permission as false, and learning/reuse permission as false. The live review form collects none of those permissions because its website submission is inactive.

Hosting, access-control, security, and operational systems may process request metadata or retain logs outside this application code. Their exact fields, locations, subprocessors, and retention periods have not been verified here.

The legal controller/record owner, future production processor, real retention/deletion rules, rights-request procedure, notification path, spam controls, and response ownership remain unresolved. No real form activation should occur until those decisions are verified.

Because the application creates no inquiry record in the current flow, it has no stored form record to access, correct, or delete. For questions about this boundary, use Email Signal Trapper; that route does not establish a complete production rights process.