Check bilingual inquiry wording and routing
paired-page-text.txt
BLANK INPUT: complete from acquired, approved evidence

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.

REQUIRED SECTIONS
capture_id; URL; locale/declared_language; captured_at; source_ref
[Complete from the source. If unavailable, write unknown and explain the gap.]

form_id and route_key where verified
[Complete from the source. If unavailable, write unknown and explain the gap.]

segment_id; translation_id; exact visible text; page section/field identifier
[Complete from the source. If unavailable, write unknown and explain the gap.]

IF EVIDENCE IS MISSING
Stop the dependent comparison or mark affected scope explicitly incomplete.

VALIDATION RULES
- 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.

Read START-HERE.txt and NATIVE-INPUT-MAPPING.txt for source acquisition, privacy gates and the exact handoff. Include this completed input wherever the prompt expects it; a file that was not loaded or pasted is not AI-visible.