LEGACY ROUTE ONLY
These files preserve the earlier prepared-input review route and its invented examples. They do not satisfy or test the upgraded closure-register/request-ledger workflow. Start with ../README.txt and ../START-HERE.txt for the current route. Do not combine the two schemas or use the old expected results as automation test evidence.

G16: native input mapping
Prepare neutral review invitations

Purpose and compatibility
A blank file is an input scaffold, not a native export or completed mapping. Preserve the exact column names/order and input names. Populate only from the documented native acquisition or explicit manual evidence. Stop if a required input, permission, privacy condition or coverage requirement is missing. Do not replace an old prompt until the named inputs and field-level mapping are reviewed. These files do not authorize login, setup, imports, account changes, message sending, publication, test submissions or spending.
Contract status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible
Compatible without mapping: false

Required inputs
Eligibility -> native-eligibility-template.csv
Exact columns: alias,milestone,contact_permission,opted_out,prior_request_sent,coverage,source_ref
Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts.

ApprovedPolicy -> native-approvedpolicy-template.txt
Required content: Full uniform request policy, approved milestone/contact rules, privacy and duplicate-request rules.
Complete each required field from approved source evidence.

VerifiedLink -> native-verifiedlink-template.txt
Required content: Actual copied review-request URL and correct profile/location verification.
Complete each required field from approved source evidence.

Scope -> native-scope-template.txt
Required content: Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file.
Complete each required field from approved source evidence.

Old files and reviewed mapping
invitation-draft.txt
Original first line: EMPTY OUTPUT TEMPLATE: invitation-draft.txt

invitation-queue.csv
Original first line: service_alias,eligibility,reason,prior_request_ref,channel,reviewer_status

request-log.csv
Original first line: service_alias,requested_at,channel

services.csv
Original first line: service_alias,milestone,milestone_at,contact_permission,opted_out

uniform-policy.txt
Original first line: G16: uniform-policy.txt

services.csv -> Eligibility: verify service_alias -> alias, milestone, contact_permission and opted_out. request-log.csv may establish prior_request_sent only after complete request-history inspection. Add coverage and source_ref; missing permission/history remains blocked.
uniform-policy.txt -> ApprovedPolicy and Scope: carry the complete uniform milestone, contact, privacy and duplicate-request policy. invitation-queue.csv and invitation-draft.txt are old outputs. Ratings, complaints and outcomes cannot be selection criteria.
VerifiedLink requires the actual copied review-request URL and correct profile/location verification; no old starter file supplies a genuine URL automatically.

How to perform the handoff
1. Keep original exports and raw evidence unchanged in restricted firm storage. Check actual source fields, dates, coverage, privacy and access before mapping.
2. Prepare the distinct native inputs above. Record every mapped field, derived interpretation, missing value and observed source reference in Scope. Identically named columns still require source/evidence validation.
3. Create a separate minimized analysis workbook or text packet. Name tables/sections exactly as listed. A CSV file does not itself create a named Excel table.
4. Include the full completed Scope in the same AI-visible workbook or pasted packet. Verify exclusions, denominator, matching rules and unknowns. Do not hide raw client data on another worksheet.
5. Obtain the responsible reviewer’s approval of the completed mapping and evidence coverage before using the native prompt. Keep all blocked items visible. Any later external action is a separately authorized human step.

Acquisition and privacy requirements
Use approved minimized administrative metadata and aliases only. Aliases alone do not guarantee anonymity. Keep untouched exports/screenshots, identifying source maps, full documents and sensitive narratives in restricted firm storage. A hidden worksheet is not a privacy boundary. Do not insert credentials, payment/tax identifiers, raw client documents or unsanitized review text. Unknown is not zero, false, completed or absent.
Existing authorized access to the correct source account and records; no new login, credentials, installation or permission grant is included.
Responsible lawyer/operations reviewer approves scope, definitions and any later action.
AI optional; use only approved minimized data and retain originals separately.
Permission, milestone and prior-request fields are not guaranteed native exports. No review solicitation automation is activated.
The live account, entitlement, exact headers, records and field coverage have not been observed.

Recipe acquisition / manual mapping instructions
Copy the genuine profile review link
Location: Business Profile > Read reviews > Get more reviews > Copy
Use the correct existing firm/location profile. Copy the actual review-request link and check its destination. A desktop browser also supports saving the displayed QR image.
Verification: An individual review Share link is different from the link that requests a new review.
https://support.google.com/business/answer/16816815?hl=en-GB

Capture eligibility without sentiment gating
Location: Existing targeted Custom Report and selected matter Tasks/Activities; firm’s approved request log
Capture only the uniformly defined service milestone, contact-permission flag, opt-out state and whether a request was already sent. Exact fields are firm-maintained; inspect source records when they do not exist in a report. Do not use ratings, complaints or outcomes as selection criteria.
Verification: No invitation is inferred from Hired status or absence of a logged opt-out; unknown permission is blocked.
https://help.lawmatics.com/en/articles/10699825-matter-profile-overview
https://help.lawmatics.com/en/articles/10738648-completing-and-editing-tasks
https://support.google.com/contributionpolicy/answer/7400114?hl=en


Do not proceed when
- Missing uniform policy, verified link, complete request history or affirmative permitted-contact evidence.

Scope template requirements
Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file.

Old examples and validation limits
Legacy synthetic examples and negative cases belong to their old prompts. They do not automatically test the native route and must not be fed into a new prompt without an explicit reviewed mapping and separately approved test design. These new files contain no synthetic values, source exports, account results or live-test evidence.
Documentation-checked component path; proposed workflow, not tested
Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed.
Local validation covers only exact scaffold schemas, placeholder presence, blank CSV rows and required warnings. It does not establish live account coverage, native export validity, successful integration or completed workflow tests.
