Reconcile certified-mail tracking with return-receipt evidence 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 - Electronic return receipt availability depends on the purchased service and completed signature record. A missing service/number/receipt is an explicit blocker. - Physical return-card tracking is not a downloadable image of the signed card. - Provider/geography boundary: this is a USPS United States-service evidence path subject to the purchased service and destination. It does not establish another carrier or international postal receipt workflow. MAP THE ACTUAL SOURCE TO THE REVIEW INPUT Original article number → internally assigned article_token; purchased service/date → mailings.csv. Visible status/time → tracking.csv, preserving timezone/unknown date. Actual return receipt’s delivery/receipt fields → receipts.csv with locator; do not label capture date as delivery date. Staff supplies owner_alias and approved_review_interval_days; no rule-derived period. INPUTS THE ASSISTANT MAY READ mailings.csv; tracking.csv; receipts.csv; receipt-evidence-notes.txt; 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: mailings.csv type: csv headers: - mail_id - matter_alias - article_token - mailing_date - service_purchased - approved_review_interval_days - owner_alias required: True templateFilename: native-mailings-template.csv existingKitFiles: - mailings.csv compatibility: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference. inputName: mailings.csv compatibleWithoutMapping: True - name: tracking.csv type: csv headers: - article_token - latest_status - status_time - source_ref required: True templateFilename: native-tracking-template.csv existingKitFiles: - tracking.csv compatibility: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference. inputName: tracking.csv compatibleWithoutMapping: True - name: receipts.csv type: csv headers: - article_token - receipt_date - receipt_locator - source_ref required: True templateFilename: native-receipts-template.csv existingKitFiles: - receipts.csv compatibility: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference. inputName: receipts.csv compatibleWithoutMapping: True - name: receipt-evidence-notes.txt type: text requiredSections: - article_token and restricted crosswalk held elsewhere - purchased USPS service and source token - mailpiece versus return-card identifier distinction - tracking status time/timezone; receipt_date field meaning and actual source value - actual receipt locator; signature/image inspected by human; unresolved association gaps required: True templateFilename: native-receipt-evidence-notes-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: receipt-evidence-notes.txt sections: - article_token and restricted crosswalk held elsewhere - purchased USPS service and source token - mailpiece versus return-card identifier distinction - tracking status time/timezone; receipt_date field meaning and actual source value - actual receipt locator; signature/image inspected by human; unresolved association gaps 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: - The legacy receipt_date is ambiguous without this companion: explicitly state whether it means delivery date, mailroom receipt date or source-issued date. Never silently substitute capture time. 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: - mailings.csv nativeInput: mailings.csv mapping: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns. compatibleWithoutMapping: True - existingKitFiles: - tracking.csv nativeInput: tracking.csv mapping: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns. compatibleWithoutMapping: True - existingKitFiles: - receipts.csv nativeInput: receipts.csv mapping: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns. compatibleWithoutMapping: True additionalEvidence: - receipt-evidence-notes.txt - 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. mailings.csv: native-mailings-template.csv tracking.csv: native-tracking-template.csv receipts.csv: native-receipts-template.csv receipt-evidence-notes.txt: native-receipt-evidence-notes-template.txt manifest.txt: native-manifest-template.txt evidence-map.csv: native-evidence-map-template.csv STEP 1: Capture the mailpiece tracking and existing receipt separately Tool: USPS Tracking and existing mailed/electronic receipt Open: USPS Tracking > enter original article number; existing return-receipt PDF or PS Form 3811 The mailroom operator uses the original mailing receipt to identify the mailpiece article number, captures its displayed status/date and opens the already-received electronic proof-of-delivery attachment or scans the actual green card. Preserve the purchased-service receipt. USPS documents an electronic-return-receipt request after delivery, but this recipe only flags that human next step; it does not submit an email address or request a new receipt. Expected output: Original mailing/tracking/receipt evidence with distinct identifiers Use it next: Map article numbers to neutral tokens in a restricted crosswalk. Check: The green-card Related Tracking Number tracks the returning card, not the original mailpiece. Delivered tracking is not automatically a return receipt or valid legal service. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://faq.usps.com/articles/Knowledge/What-is-Electronic-Return-Receipt https://faq.usps.com/articles/Knowledge/Return-Receipt-The-Basics STEP 2: 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: Original article number → internally assigned article_token; purchased service/date → mailings.csv. Visible status/time → tracking.csv, preserving timezone/unknown date. Actual return receipt’s delivery/receipt fields → receipts.csv with locator; do not label capture date as delivery date. Staff supplies owner_alias and approved_review_interval_days; no rule-derived period. 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 mailings.csv; tracking.csv; receipts.csv; receipt-evidence-notes.txt; 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://faq.usps.com/articles/Knowledge/What-is-Electronic-Return-Receipt https://faq.usps.com/articles/Knowledge/Return-Receipt-The-Basics STEP 3: 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 4: 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 Join only exact article_token. Return delivered-without-receipt, missing tracking, mismatched receipt, duplicate token and conflicting-date exceptions with source references. Distinguish mailpiece tracking from return-card tracking. Preserve raw status and date meanings. Use only staff-approved review intervals for administrative follow-up flags. Do not infer service validity, compute legal deadlines, request a refund or receipt, send email or alter the mailing record. Expected output: certified-mail-evidence-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 5: 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 certified-mail-evidence-review.csv. Mailroom owner checks original service purchase and receipt association. Lawyer determines any legal sufficiency or service consequence; requesting missing evidence is a separately authorized action. Expected output: Source-checked certified-mail-evidence-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): Delivered mailpiece with only the returning-card barcode remains missing return-receipt evidence. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://faq.usps.com/articles/Knowledge/What-is-Electronic-Return-Receipt https://faq.usps.com/articles/Knowledge/Return-Receipt-The-Basics STEP 6: Approve the internal next action Tool: Responsible human owner Open: Existing internal work queue / approved source system Record the reviewer, decision and unresolved blockers. Mailroom owner checks original service purchase and receipt association. Lawyer determines any legal sufficiency or service consequence; requesting missing evidence is a separately authorized action. 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://faq.usps.com/articles/Knowledge/What-is-Electronic-Return-Receipt https://faq.usps.com/articles/Knowledge/Return-Receipt-The-Basics ACCOUNT AND SOURCE CHECKS STILL NEEDED - Electronic return receipt availability depends on the purchased service and completed signature record. A missing service/number/receipt is an explicit blocker. - Physical return-card tracking is not a downloadable image of the signed card. - Provider/geography boundary: this is a USPS United States-service evidence path subject to the purchased service and destination. It does not establish another carrier or international postal receipt workflow. EXPECTED SYNTHETIC CHECK (NOT RUN) Delivered mailpiece with only the returning-card barcode remains missing return-receipt evidence. 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.