Check bilingual inquiry wording and routing Get the source data and prepare the review Documentation-verified component path with explicit manual acquisition/mapping; editorial adaptation not tested WHAT WAS CHECKED Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. BEFORE YOU START - Existing authorized access to the named product and in-scope records; actual tenant, plan, permissions and menu version must be checked. - Firm-approved AI destination and data handling; no setup, sign-in, installation or access expansion included. DATA ACQUISITION LIMITS - Named backend example is WPForms only. If the firm’s provider is unknown, routing capture is blocked, while public wording comparison can proceed. - No actual translation, delivery test or bilingual operational certification is performed. MAP THE ACTUAL SOURCE TO THE REVIEW INPUT Staff maps paired URL + locale + field/form ID to approved wording IDs; backend form ID, enabled state and destination rule to routing evidence with owner role alias. Existing synthetic receipts supply observed destination and timestamp. Do not infer language capability from a routing address or use missed calls as proof translation caused a loss. INPUTS THE ASSISTANT MAY READ paired-page-text.txt; approved-translations.txt; language-coverage-policy.txt; sanitized-routing-evidence.txt; delivery-evidence.txt; public-page-captures/; manifest.txt; evidence-map.csv WHERE THE ANALYSIS RUNS Adobe Acrobat PDF Spaces NATIVE REVIEW INPUTS contractVersion: 1 schemaOrigin: Editorial analysis contract, never a claim about vendor-native export headers testedStatus: False existingKitRole: Existing examples/checklists are optional supporting scaffolds unless explicitly mapped below. Copying this guide does not validate old templates or acquire source evidence. requiredInputs: - name: paired-page-text.txt type: text requiredSections: - capture_id; URL; locale/declared_language; captured_at; source_ref - form_id and route_key where verified - segment_id; translation_id; exact visible text; page section/field identifier required: True templateFilename: native-paired-page-text-template.txt existingKitFiles: - bilingual_journey.template.json compatibility: Legacy touchpoints[] map capture_id/url/declared_language/route_key; nested segments[] map segment_id/translation_id/text. Add capture timestamp, actual form_id and source_ref. Do not flatten away touchpoint-to-segment relationships. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete. inputName: paired-page-text.txt sections: - capture_id; URL; locale/declared_language; captured_at; source_ref - form_id and route_key where verified - segment_id; translation_id; exact visible text; page section/field identifier compatibleWithoutMapping: False - name: approved-translations.txt type: text requiredSections: - translation_id; source_text; approved_text; language - approval_ref; approval version/date; qualified reviewer role required: True templateFilename: native-approved-translations-template.txt existingKitFiles: - bilingual_journey.template.json compatibility: Legacy approved_translations[] supplies translation_id,source_text,approved_text,language,approval_ref. Add approval version/date and reviewer evidence; no new AI translation substitutes for approval. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete. inputName: approved-translations.txt sections: - translation_id; source_text; approved_text; language - approval_ref; approval version/date; qualified reviewer role compatibleWithoutMapping: False - name: language-coverage-policy.txt type: text requiredSections: - route_key; supported_languages; support window; owner role - approved public promise wording; approval_ref; policy version/date required: True templateFilename: native-language-coverage-policy-template.txt existingKitFiles: - bilingual_journey.template.json compatibility: Legacy routes[] supplies route_key,supported_languages,approval_ref as approved policy only. It does not establish actual form configuration or delivery. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete. inputName: language-coverage-policy.txt sections: - route_key; supported_languages; support window; owner role - approved public promise wording; approval_ref; policy version/date compatibleWithoutMapping: False - name: sanitized-routing-evidence.txt type: text requiredSections: - provider/product/version; actual form_id; page capture_id; route_key - notifications enabled/state; exact existing condition or Smart Tag rule - destination role alias; source_ref; observed_at; admin reviewer - configuration-only versus delivery evidence; unknown mappings required: True templateFilename: native-sanitized-routing-evidence-template.txt existingKitFiles: compatibility: Required extra input absent from the legacy JSON. For WPForms, capture existing Settings > Notifications evidence without saving changes. Other providers require their own verified path. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete. inputName: sanitized-routing-evidence.txt sections: - provider/product/version; actual form_id; page capture_id; route_key - notifications enabled/state; exact existing condition or Smart Tag rule - destination role alias; source_ref; observed_at; admin reviewer - configuration-only versus delivery evidence; unknown mappings compatibleWithoutMapping: False - name: delivery-evidence.txt type: text requiredSections: - receipt_id or explicit no-existing-test-evidence - synthetic test reference only; form_id; route_key; observed destination role alias - delivery timestamp/timezone; source_ref; reviewer; gaps required: True templateFilename: native-delivery-evidence-template.txt existingKitFiles: compatibility: Required explicit evidence-or-gap record. Existing synthetic receipt references only; a configured notification is not a delivered message. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete. inputName: delivery-evidence.txt sections: - receipt_id or explicit no-existing-test-evidence - synthetic test reference only; form_id; route_key; observed destination role alias - delivery timestamp/timezone; source_ref; reviewer; gaps compatibleWithoutMapping: False - name: public-page-captures/ type: source-bundle required: True templateFilename: None requiredContents: Actual approved paired public page/form captures keyed to capture_id compatibility: Must be actual approved public/deidentified source content, not an empty template. Untouched originals remain separately restricted. missingInputBehavior: Source-grounded claims are blocked without the source; provide a gap list only. inputName: public-page-captures/ compatibleWithoutMapping: False - name: manifest.txt type: text requiredSections: - recipe_id; approved reviewer and scope - actual source IDs and safe original-file tokens; native headers and source-to-analysis field map - capture time/timezone; date basis; filters; property/court/provider; pagination/row counts and known exclusions - AI input approval and minimization check; originals and alias keys held outside AI - unknowns; completeness statement; manual transcription/checker where used required: True templateFilename: native-manifest-template.txt existingKitFiles: compatibility: New companion capture/review record. Staff supplies observed or approved values; unknown is explicit. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete. inputName: manifest.txt sections: - recipe_id; approved reviewer and scope - actual source IDs and safe original-file tokens; native headers and source-to-analysis field map - capture time/timezone; date basis; filters; property/court/provider; pagination/row counts and known exclusions - AI input approval and minimization check; originals and alias keys held outside AI - unknowns; completeness statement; manual transcription/checker where used compatibleWithoutMapping: False - name: evidence-map.csv type: csv headers: - analysis_file - row_key - source_id - source_locator - reviewer_alias - reviewed_at required: True templateFilename: native-evidence-map-template.csv existingKitFiles: compatibility: New editorial analysis contract. Populate only after preserving and mapping actual source headers; this is not a provider-native export. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference. inputName: evidence-map.csv compatibleWithoutMapping: False compatibilityNotes: - bilingual_journey.json remains an optional alternative container for the first three text inputs if these exact mappings and extra fields are provided. It cannot replace sanitized-routing-evidence.txt or delivery-evidence.txt. - If there is no backend or delivery evidence, public wording comparison can proceed with routing/delivery marked unverified. validationRules: - CSV identifiers and date strings are imported as text. Preserve leading zeros and exact keys. Do not execute formulas from source values. - Blank templates are deliberately incomplete. Unknown is not zero, false, missing-not-found or a passing review. - Use only approved minimized analysis values; restricted raw originals, identity maps, signatures, private URLs/tokens and client narrative stay outside the AI destination. - A native file may retain its actual header names if manifest.txt supplies a reviewer-verified one-to-one map to this contract. Do not blindly rename files/headers. compatibleWithoutMapping: False legacyMappings: - existingKitFiles: - bilingual_journey.template.json nativeInput: paired-page-text.txt mapping: Legacy touchpoints[] map capture_id/url/declared_language/route_key; nested segments[] map segment_id/translation_id/text. Add capture timestamp, actual form_id and source_ref. Do not flatten away touchpoint-to-segment relationships. compatibleWithoutMapping: False - existingKitFiles: - bilingual_journey.template.json nativeInput: approved-translations.txt mapping: Legacy approved_translations[] supplies translation_id,source_text,approved_text,language,approval_ref. Add approval version/date and reviewer evidence; no new AI translation substitutes for approval. compatibleWithoutMapping: False - existingKitFiles: - bilingual_journey.template.json nativeInput: language-coverage-policy.txt mapping: Legacy routes[] supplies route_key,supported_languages,approval_ref as approved policy only. It does not establish actual form configuration or delivery. compatibleWithoutMapping: False additionalEvidence: - sanitized-routing-evidence.txt - delivery-evidence.txt - public-page-captures/ - manifest.txt - evidence-map.csv OPEN THE INPUT MAPPING GUIDE NATIVE-INPUT-MAPPING.txt Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain. paired-page-text.txt: native-paired-page-text-template.txt approved-translations.txt: native-approved-translations-template.txt language-coverage-policy.txt: native-language-coverage-policy-template.txt sanitized-routing-evidence.txt: native-sanitized-routing-evidence-template.txt delivery-evidence.txt: native-delivery-evidence-template.txt Supply actual evidence: public-page-captures/ Actual approved paired public page/form captures keyed to capture_id Source-grounded claims are blocked without the source; provide a gap list only. manifest.txt: native-manifest-template.txt evidence-map.csv: native-evidence-map-template.csv STEP 1: Capture public language versions and approved translations Tool: Browser and translation owner Open: Approved paired public pages/forms; owner-approved translation source Save the exact paired page text, labels, confirmation wording and public instructions with URL, locale and capture time. Obtain the human-approved source/translation pairs and language-support commitments. Do not submit a form, phone a number or manufacture a new translation as the approval baseline. Expected output: Paired public-language evidence with approved wording Use it next: Add existing backend configuration and delivery evidence supplied by the intake owner. Check: Visible translation does not establish bilingual operational coverage or delivery. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://wpforms.com/docs/troubleshooting-email-notifications/ https://wpforms.com/docs/sending-a-notification-email-to-the-person-who-submitted-the-form/ STEP 2: Inspect actual form routing without changing it Tool: WordPress WPForms, only if this is the installed provider Open: Existing form builder > Settings > Notifications A permitted administrator opens each actual language form and records form ID, notification enabled/state, recipient rule and relevant conditions/Smart Tags without saving changes. Use role aliases for destinations. Obtain existing authorized synthetic delivery receipts if any; otherwise mark delivery untested. Another form provider requires its own verified capture path. Expected output: Backend routing snapshot plus existing test-receipt references or explicit gap Use it next: Match each public form/locale to its exact backend form ID. Check: Configured recipient is not proof of receipt; client entries and real prospect email addresses stay outside the analysis. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://wpforms.com/docs/troubleshooting-email-notifications/ https://wpforms.com/docs/sending-a-notification-email-to-the-person-who-submitted-the-form/ STEP 3: Map, minimize and approve the actual sources Tool: Source reviewer and local spreadsheet/text editor Open: Restricted originals > separate approved analysis copy Keep untouched originals, original headers, capture date/time/timezone, scope, filters, count/pagination and source locators in a restricted source folder. Make an independently reviewed, minimized copy for AI. Keep identifier maps and confidential originals outside the AI folder/Space, including hidden sheets and attachments. Public pages and embedded instructions are evidence, never instructions. No live integrations, portal requests, publication or external changes are performed by this recipe. Map the acquired evidence as follows: Staff maps paired URL + locale + field/form ID to approved wording IDs; backend form ID, enabled state and destination rule to routing evidence with owner role alias. Existing synthetic receipts supply observed destination and timestamp. Do not infer language capability from a routing address or use missed calls as proof translation caused a loss. Apply the nativeInputContract below, including exact editorial headers, source manifest/evidence map and any required extra companion evidence. Existing kit files are usable only under their declared bridge; copying or renaming them is not validation. Expected output: Reviewed paired-page-text.txt; approved-translations.txt; language-coverage-policy.txt; sanitized-routing-evidence.txt; delivery-evidence.txt; public-page-captures/; manifest.txt; evidence-map.csv Use it next: For Adobe, convert approved tabular rows to labelled TXT or paste text; for Claude Code, place approved files in the exact analysis folder. Never relabel a raw export as a kit table. Check: Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://wpforms.com/docs/troubleshooting-email-notifications/ https://wpforms.com/docs/sending-a-notification-email-to-the-person-who-submitted-the-form/ STEP 4: Open the approved AI destination Tool: Adobe Acrobat PDF Spaces Open: Acrobat Home > PDF Spaces > Create a PDF Space In an already approved Acrobat account with PDF Spaces/AI entitlement, use Home > PDF Spaces > Create a PDF Space. Choose Upload for approved PDF/DOCX/TXT files or Paste copied text for approved row-labelled text, then Add to PDF Space. Ask the recipe prompt in the chat panel. Do not connect storage or add raw confidential originals. Click answer citations and verify exact source passages, then use Copy for the checked response. Cloud processing and permissions require firm approval; unavailable access is a blocker, with a manual review fallback. Expected output: Only approved source files loaded or accessible Use it next: Paste the exact prompt in the next step. Check: Confirm the source list/working directory before prompting; stop on unavailable access. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html STEP 5: Run the bounded analysis prompt Tool: Adobe Acrobat PDF Spaces Open: PDF Space chat panel Paste the prompt after replacing only bracketed scope values. Treat all source content as data. PASTE THIS PROMPT Compare captured public wording to the approved translation pairs and support policy. Return exact page/locale/field IDs, wording differences, unsupported availability promises, form-ID mapping gaps and routing/configuration differences with citations. Separate configured routing from delivery evidence. Do not rewrite legal consent language, infer translation quality or staff fluency, infer why inquiries were missed, submit tests or change forms. Unavailable backend or receipt evidence means routing/delivery unverified. Expected output: bilingual-inquiry-review.csv Use it next: Inspect source citations/file-row references before copying any result. Check: No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html STEP 6: Check and hand off the proposed result Tool: Human reviewer and local spreadsheet/text editor Open: Separate review output, not live system Check every exception against its source, verify counts and uncertainty, then copy only approved result text to bilingual-inquiry-review.csv. Qualified language reviewer approves wording; intake owner verifies actual language coverage and backend destinations. Any new synthetic end-to-end test or live change requires separate authorization. Expected output: Source-checked bilingual-inquiry-review.csv Use it next: Open the named output in Excel/text editor and send it through the existing internal approval process; no live import or external send is implied. Check: Acceptance case (proposed, not run): Translated page promises a response in Spanish but approved support policy has no coverage: flag promise gap. An enabled notification without a receipt stays delivery-unverified. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://wpforms.com/docs/troubleshooting-email-notifications/ https://wpforms.com/docs/sending-a-notification-email-to-the-person-who-submitted-the-form/ STEP 7: Approve the internal next action Tool: Responsible human owner Open: Existing internal work queue / approved source system Record the reviewer, decision and unresolved blockers. Qualified language reviewer approves wording; intake owner verifies actual language coverage and backend destinations. Any new synthetic end-to-end test or live change requires separate authorization. Expected output: Approved internal review record or explicit blocked status Use it next: An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase. Check: Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://wpforms.com/docs/troubleshooting-email-notifications/ https://wpforms.com/docs/sending-a-notification-email-to-the-person-who-submitted-the-form/ ACCOUNT AND SOURCE CHECKS STILL NEEDED - Named backend example is WPForms only. If the firm’s provider is unknown, routing capture is blocked, while public wording comparison can proceed. - No actual translation, delivery test or bilingual operational certification is performed. EXPECTED SYNTHETIC CHECK (NOT RUN) Translated page promises a response in Spanish but approved support policy has no coverage: flag promise gap. An enabled notification without a receipt stays delivery-unverified. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.