START WITH THE PRODUCT STEPS
Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration.

G17 - Prepare a Google profile reinstatement review
Status: Proposed / not tested

WHAT THIS KIT DOES
Provides exact-header blank CSVs, separate fabricated examples, required text-input scaffolds, and expected output examples for one offline review. It does not configure an integration or run a workflow.

PREREQUISITES
1. Actual suspension notice, verified business information, eligible operational location/service model, firm-approved evidence files; manual appeal submission.
2. Use synthetic inputs first. Real records require firm-approved access, processing terms, retention, and confidentiality controls. IDs alone do not anonymize a record.
3. Verify product plan, available exports, coverage, and the named reviewer. The prompt does not configure an integration.
Name a reviewer and keep actual prospect/client data within firm-approved systems. IDs alone are not anonymization.

INPUTS
- suspension-notice.txt: profile alias, notice date, exact stated issue and source reference
- business-facts.csv: fact_id, fact_name, verified_value, evidence_ref, verified_at
- evidence.csv: evidence_id, evidence_type, source_ref, available, discrepancy; eligibility-policy.txt: current official eligibility rules and sources, evidence submission timing, firm-approved disclosure scope

OUTPUT SHAPE
reinstatement-readiness.csv: fact_id, requirement, evidence_refs, contradiction_or_gap, readiness, human_next_step; appeal-draft.txt: factual draft only when supplied verified facts support eligibility

SETUP AND FIRST TRIAL
1. Keep the original exports unchanged. Copy this kit into an approved working folder.
2. Start with only the files ending -example. They contain fabricated data. CSV files without -example contain headers only; text inputs without -example contain empty preparation scaffolds.
3. For the synthetic trial, copy each example into a separate trial folder under its canonical input filename. Do not mix example rows with real exports. Supply the matching example policies too. Output examples are for comparison after drafting, not evidence inputs.
4. Import CSVs as UTF-8 comma-delimited data. Preserve identifiers as text and date/timestamp strings in their specified ISO format. Boolean examples use true/false. Empty cells mean unknown or not supplied, never automatic zero/no. Amounts are numeric; use the stated currency and do not combine currencies. No formulas or macros are included.
5. Paste starter-prompt.txt into the firm's approved assistant with only the input files. A staff member can also perform the comparison in a spreadsheet. No account connector is needed for this file-based trial.
6. Check the draft against fixture-expectations.txt and the matching output examples. Use exact arithmetic in native spreadsheet tools or code and inspect source IDs manually. An AI response has not been run or validated for this kit.
7. Resolve missing policies, uncertainty, permissions and coverage with the named reviewer. Live platform configuration, messages, uploads and other changes require their own approval and testing.

FIXTURE TARGET
Mailing-only evidence creates a readiness block; unknown signage remains a gap. No eligible office, staffing or document is invented. No affirmative appeal draft or timed form is opened.

LIMITS
- No duplicate replacement profiles, fake locations or rule evasion. Do not adopt misleading forum workarounds; no guarantee of reinstatement. Sharing identifying business records requires approval and redaction of unrelated personal data.
- Only file/header and synthetic fixture consistency are checked. No workflow, connector, AI response, product feature or integration is tested.
- Every example is fabricated. IDs alone do not anonymize actual firm data. Use approved minimized data, access, processing terms and retention controls.
Source-policy text scaffolds are not legal advice or production configuration. No real review link, phone destination, contact address, API token or credential is included in examples. example.invalid and fixture: references are deliberate non-live placeholders.

SOURCES
Pain evidence: Public discussion: https://www.reddit.com/r/LawFirm/comments/1mudpvm/google_business_profile/
Method: Official method documentation: https://support.google.com/business/answer/4569145?hl=en-419
Method: Official method documentation: https://support.google.com/business/answer/3038177?version=published

VALIDATION SCOPE
Header and fixture validation passed; workflow not tested. Read the exact checks and limits in fixture-expectations.txt.