G18: native input mapping Inventory marketing-account control before an agency handover 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 Assets -> native-assets-template.csv Exact columns: asset_alias,platform,scope_id_alias,firm_role,agency_role,billing_entity_alias,contract_ref,access_evidence_ref,coverage Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. Contracts -> native-contracts-template.csv Exact columns: asset_alias,approved_ownership_summary,evidence_ref,coverage Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. 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 access-evidence.csv Original first line: evidence_id,asset_id,principal_alias,organization_role,platform_role,observed_at,source_ref assets.csv Original first line: asset_id,platform,account_alias,expected_firm_role,dependency_asset_ids contract-excerpts.csv Original first line: excerpt_id,asset_id,excerpt_text,source_ref handover-inventory.csv Original first line: asset_id,observed_control,evidence_refs,missing_access_evidence,dependency_gaps,draft_request,reviewer_status scope.txt Original first line: G18: scope.txt assets.csv plus access-evidence.csv -> Assets: verify asset_id -> asset_alias, platform and account_alias -> scope_id_alias. expected_firm_role is an expectation, not observed firm_role. Capture current firm/agency roles, inherited relationships, coverage and access_evidence_ref from actual provider records. contract-excerpts.csv -> Contracts: obtain a human-approved ownership summary and evidence_ref for each asset_alias; raw excerpt_text is not automatically approved for AI. Capture coverage. Billing entity aliases and contract_ref require their actual records; omit payment/tax details. scope.txt -> Scope: retain dependencies, current observation time and provider-specific access limits. handover-inventory.csv is an old output. A Google control path cannot establish control on another provider, and observed access is not legal ownership. 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. Verified Google-side paths do not verify other vendors. Legal ownership and portability require contractual evidence. The live account, entitlement, exact headers, records and field coverage have not been observed. Recipe acquisition / manual mapping instructions Read platform-specific access screens Location: Ads/LSA: Admin > Access and security; GBP: More > Business Profile settings > People and access; GA4: Admin > Account/Property access management; GTM: Admin > Account and Container > User Management Capture current account/property/container IDs, firm/agency role aliases, pending invites and relevant inherited manager relationships without changing anything. Separately note the paying entity from permitted billing records, omitting payment/tax details. Verification: Access is not legal ownership. GA4/GTM account and property/container permissions differ; a payment role does not prove asset control. https://support.google.com/google-ads/answer/6372672?hl=en https://support.google.com/localservices/answer/7652468?hl=en https://support.google.com/business/answer/3403100?hl=en https://support.google.com/analytics/answer/9305587?hl=en https://support.google.com/tagmanager/answer/6107011?hl=en Make the checked, minimized handoff Location: Restricted original workbook > separate analysis workbook > Scope worksheet Human records each asset and source screenshot. For domain, hosting, tracking numbers, Meta or any other provider, obtain that actual provider’s read-only control evidence and official instructions first. No generic Google menu is substituted. Keep untouched original exports/screenshots and the identifying source map in restricted firm storage. Build a separate minimized analysis file; do not hide raw client data on another tab. Include the complete Scope/coverage note in the AI-visible workbook or prompt. Use aliases and administrative metadata only. Unknown is not zero, false, completed or absent. Verification: Every field has an observed source or an explicit missing reason; staff assignments are marked editorial, not native. https://support.microsoft.com/en-us/excel/merge-queries-power-query https://support.google.com/google-ads/answer/9978556?hl=en Do not proceed when - Missing correct account scope, uninspected role/inheritance or provider-specific evidence for any critical asset. 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.