plan-clio-grow-intake-followup: Scope

Blank approved text input. Replace each placeholder only with approved source information.

Required content (contract wording):
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.

Required fields:
Full approved scope: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
source account aliases: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
date filters: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
date basis/timezone: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
as-of capture time: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
definitions: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
source-to-alias map provenance: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
matching rules: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
inspected/excluded records: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
permission/privacy limits: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
missing-data reasons: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
coverage: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
responsible reviewer: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
recipe-specific policies: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
versions: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]
tests: [required: supply approved information and source evidence; if missing, record the gap and keep the affected analysis blocked]

Scope and evidence rules:
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.
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.
Include this completed Scope inside the workbook or pasted packet the AI actually receives. Keeping it in a separate unprovided file does not satisfy the input contract.
Record exact source-field-to-editorial-field mappings, excluded records, missing reasons and any ambiguous joins. Keep the private identity map out of the AI packet.

Recipe-specific scope checks:
- intake-plan-inputs-template.txt and input-preparation.txt -> ApprovedSteps and Scope: transfer only actually approved supported step types, exact asset IDs, completion events, owner roles and approvals. An available template name is not an exact verified asset ID or a completion event.
- CurrentWorkflowEvidence requires separately inspected workflow IDs, states, timestamps, errors and source references. Keep existing template rules and historical execution evidence separate. The old planning template supplies no execution test result.

Do not proceed when:
- Missing approved communication assets, exact completion events or client-contact policy.

Execution status:
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.

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.