G17: native input mapping
Prepare a Google profile reinstatement review

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
BusinessFacts -> native-businessfacts-template.csv
Exact columns: fact_id,fact_name,verified_value,evidence_ref,verified_at
Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts.

EvidenceIndex -> native-evidenceindex-template.csv
Exact columns: evidence_id,evidence_type,source_ref,available,discrepancy
Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts.

RestrictionAndPolicy -> native-restrictionandpolicy-template.txt
Required content: Captured actual restriction reason, linked current official policy excerpts and source URLs. Do not infer a reason from a generic help article.
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
appeal-draft.txt
Original first line: EMPTY OUTPUT TEMPLATE: appeal-draft.txt

business-facts.csv
Original first line: fact_id,fact_name,verified_value,evidence_ref,verified_at

eligibility-policy.txt
Original first line: G17: eligibility-policy.txt

evidence.csv
Original first line: evidence_id,evidence_type,source_ref,available,discrepancy

reinstatement-readiness.csv
Original first line: fact_id,requirement,evidence_refs,contradiction_or_gap,readiness,human_next_step

suspension-notice.txt
Original first line: G17: suspension-notice.txt

business-facts.csv -> BusinessFacts and evidence.csv -> EvidenceIndex have matching declared headers. Copy only genuinely checked, minimized facts and evidence metadata after reviewer verification; matching schemas do not validate data or prove eligibility.
suspension-notice.txt and eligibility-policy.txt -> RestrictionAndPolicy: use the actual captured restriction reason with current linked official policies and source URLs. A generic help article cannot supply the actual reason.
reinstatement-readiness.csv and appeal-draft.txt are old outputs, not source facts. Keep tax IDs, personal details and entire original documents outside the AI packet. Record contradictions and genuine missing evidence in Scope; do not submit an appeal from these scaffolds.

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.
Preparation does not establish eligibility or guaranteed reinstatement. No live restriction screen or upload limits were inspected.
The live account, entitlement, exact headers, records and field coverage have not been observed.

Recipe acquisition / manual mapping instructions
Capture the actual restriction and policy
Location: Official appeals tool linked from Google’s suspended-profile help > correct profile > restriction reason and policy link
Read the existing notice and, with already authorized account access, the displayed decision/reason. Preserve text/screenshots and date. Do not Submit Appeal or open the timed evidence form during preparation.
Verification: Do not create a replacement profile while an appeal is pending. Account restriction versus profile/content restriction needs the right route.
https://support.google.com/business/answer/4569145?hl=en

Inventory genuine proof locally
Location: Approved local registration/licence/utility records; profile name/address/service model
Human checks actual operating location, signage, staffed hours and in-person/service-area eligibility. Inventory evidence IDs, dates and name/address consistency. Keep tax IDs, personal details and entire original documents out of downstream AI.
Verification: Mail-only virtual offices are ineligible; co-working offices require qualifying signage, customer reception and the firm’s own staffing. Do not invent facts to fit rules.
https://support.google.com/business/answer/3038177?hl=en
https://support.google.com/business/answer/4569145?hl=en


Do not proceed when
- No actual suspension notice, contradictory business facts, ineligible service model or missing genuine 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.
