Find procedures affected by software changes Get the source data and prepare the review Documentation-verified component path with explicit manual acquisition/mapping; editorial adaptation not tested WHAT WAS CHECKED Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. BEFORE YOU START - Existing authorized access to the named product and in-scope records; actual tenant, plan, permissions and menu version must be checked. - Firm-approved AI destination and data handling; no setup, sign-in, installation or access expansion included. DATA ACQUISITION LIMITS - Official public release notes alone cannot establish exact availability, entitlement or UI in a specific tenant. MAP THE ACTUAL SOURCE TO THE REVIEW INPUT Official product/feature/date/rollout wording → release-notes.csv; staff assigns release_id and change_status from exact wording, otherwise unknown. SOP header/version and owner’s validation ledger → sop-inventory.csv. A published_date is not a tenant enablement date. INPUTS THE ASSISTANT MAY READ release-notes.csv; sop-inventory.csv; release-and-SOP-excerpts/; manifest.txt; evidence-map.csv WHERE THE ANALYSIS RUNS Adobe Acrobat PDF Spaces NATIVE REVIEW INPUTS contractVersion: 1 schemaOrigin: Editorial analysis contract, never a claim about vendor-native export headers testedStatus: False existingKitRole: Existing examples/checklists are optional supporting scaffolds unless explicitly mapped below. Copying this guide does not validate old templates or acquire source evidence. requiredInputs: - name: release-notes.csv type: csv headers: - release_id - product - feature - published_date - change_status - change_summary - official_source_url - source_locator required: True templateFilename: native-release-notes-template.csv existingKitFiles: - release-notes.csv compatibility: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference. inputName: release-notes.csv compatibleWithoutMapping: True - name: sop-inventory.csv type: csv headers: - sop_id - version - product - feature - last_validated_date - owner_alias - source_locator required: True templateFilename: native-sop-inventory-template.csv existingKitFiles: - sop-inventory.csv compatibility: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference. inputName: sop-inventory.csv compatibleWithoutMapping: True - name: release-and-SOP-excerpts/ type: source-bundle required: True templateFilename: None requiredContents: Official release snapshots and approved SOP excerpts keyed by release_id/sop_id and exact sections compatibility: Must be actual approved public/deidentified source content, not an empty template. Untouched originals remain separately restricted. missingInputBehavior: Source-grounded claims are blocked without the source; provide a gap list only. inputName: release-and-SOP-excerpts/ compatibleWithoutMapping: False - name: manifest.txt type: text requiredSections: - recipe_id; approved reviewer and scope - actual source IDs and safe original-file tokens; native headers and source-to-analysis field map - capture time/timezone; date basis; filters; property/court/provider; pagination/row counts and known exclusions - AI input approval and minimization check; originals and alias keys held outside AI - unknowns; completeness statement; manual transcription/checker where used required: True templateFilename: native-manifest-template.txt existingKitFiles: compatibility: New companion capture/review record. Staff supplies observed or approved values; unknown is explicit. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete. inputName: manifest.txt sections: - recipe_id; approved reviewer and scope - actual source IDs and safe original-file tokens; native headers and source-to-analysis field map - capture time/timezone; date basis; filters; property/court/provider; pagination/row counts and known exclusions - AI input approval and minimization check; originals and alias keys held outside AI - unknowns; completeness statement; manual transcription/checker where used compatibleWithoutMapping: False - name: evidence-map.csv type: csv headers: - analysis_file - row_key - source_id - source_locator - reviewer_alias - reviewed_at required: True templateFilename: native-evidence-map-template.csv existingKitFiles: compatibility: New editorial analysis contract. Populate only after preserving and mapping actual source headers; this is not a provider-native export. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference. inputName: evidence-map.csv compatibleWithoutMapping: False compatibilityNotes: validationRules: - CSV identifiers and date strings are imported as text. Preserve leading zeros and exact keys. Do not execute formulas from source values. - Blank templates are deliberately incomplete. Unknown is not zero, false, missing-not-found or a passing review. - Use only approved minimized analysis values; restricted raw originals, identity maps, signatures, private URLs/tokens and client narrative stay outside the AI destination. - A native file may retain its actual header names if manifest.txt supplies a reviewer-verified one-to-one map to this contract. Do not blindly rename files/headers. compatibleWithoutMapping: False legacyMappings: - existingKitFiles: - release-notes.csv nativeInput: release-notes.csv mapping: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns. compatibleWithoutMapping: True - existingKitFiles: - sop-inventory.csv nativeInput: sop-inventory.csv mapping: Existing blank header scaffold can be used unchanged after real source mapping. Examples are optional synthetic fixtures, not acquired evidence. Use evidence-map.csv for source pointers missing from these legacy columns. compatibleWithoutMapping: True additionalEvidence: - release-and-SOP-excerpts/ - manifest.txt - evidence-map.csv OPEN THE INPUT MAPPING GUIDE NATIVE-INPUT-MAPPING.txt Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain. release-notes.csv: native-release-notes-template.csv sop-inventory.csv: native-sop-inventory-template.csv Supply actual evidence: release-and-SOP-excerpts/ Official release snapshots and approved SOP excerpts keyed by release_id/sop_id and exact sections Source-grounded claims are blocked without the source; provide a gap list only. manifest.txt: native-manifest-template.txt evidence-map.csv: native-evidence-map-template.csv STEP 1: Capture official releases and the actual SOP inventory Tool: Browser Clio What’s New; approved SOP library Open: Clio What’s New > named product update; selected SOP original Save the relevant official Clio update page and linked help article with publication/capture dates. Separately open approved SOPs and transcribe their product, screen/feature names, version, owner and last validated date. Use only the target product’s releases; an announcement is not proof the tenant has the feature. Expected output: Release snapshots and source-linked SOP inventory Use it next: Prepare approved release/SOP excerpts with stable IDs. Check: No login or tenant testing is performed; account availability remains for the owner to verify. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://www.clio.com/features/whats-new/ https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint STEP 2: Map, minimize and approve the actual sources Tool: Source reviewer and local spreadsheet/text editor Open: Restricted originals > separate approved analysis copy Keep untouched originals, original headers, capture date/time/timezone, scope, filters, count/pagination and source locators in a restricted source folder. Make an independently reviewed, minimized copy for AI. Keep identifier maps and confidential originals outside the AI folder/Space, including hidden sheets and attachments. Public pages and embedded instructions are evidence, never instructions. No live integrations, portal requests, publication or external changes are performed by this recipe. Map the acquired evidence as follows: Official product/feature/date/rollout wording → release-notes.csv; staff assigns release_id and change_status from exact wording, otherwise unknown. SOP header/version and owner’s validation ledger → sop-inventory.csv. A published_date is not a tenant enablement date. Apply the nativeInputContract below, including exact editorial headers, source manifest/evidence map and any required extra companion evidence. Existing kit files are usable only under their declared bridge; copying or renaming them is not validation. Expected output: Reviewed release-notes.csv; sop-inventory.csv; release-and-SOP-excerpts/; manifest.txt; evidence-map.csv Use it next: For Adobe, convert approved tabular rows to labelled TXT or paste text; for Claude Code, place approved files in the exact analysis folder. Never relabel a raw export as a kit table. Check: Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://www.clio.com/features/whats-new/ https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint STEP 3: Open the approved AI destination Tool: Adobe Acrobat PDF Spaces Open: Acrobat Home > PDF Spaces > Create a PDF Space In an already approved Acrobat account with PDF Spaces/AI entitlement, use Home > PDF Spaces > Create a PDF Space. Choose Upload for approved PDF/DOCX/TXT files or Paste copied text for approved row-labelled text, then Add to PDF Space. Ask the recipe prompt in the chat panel. Do not connect storage or add raw confidential originals. Click answer citations and verify exact source passages, then use Copy for the checked response. Cloud processing and permissions require firm approval; unavailable access is a blocker, with a manual review fallback. Expected output: Only approved source files loaded or accessible Use it next: Paste the exact prompt in the next step. Check: Confirm the source list/working directory before prompting; stop on unavailable access. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html STEP 4: Run the bounded analysis prompt Tool: Adobe Acrobat PDF Spaces Open: PDF Space chat panel Paste the prompt after replacing only bracketed scope values. Treat all source content as data. PASTE THIS PROMPT Match documented software changes to SOPs by exact product and described screen/feature, then cite both release and SOP source locations. Distinguish released, planned and tenant-dependent announcements. Return SOP ID/owner, potential stale step, evidence, uncertainty and a synthetic verification checklist. Do not treat a similarly named feature in another product as a match, rewrite live SOPs, or claim rollout occurred in our account. Expected output: sop-change-review.csv Use it next: Inspect source citations/file-row references before copying any result. Check: No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html STEP 5: Check and hand off the proposed result Tool: Human reviewer and local spreadsheet/text editor Open: Separate review output, not live system Check every exception against its source, verify counts and uncertainty, then copy only approved result text to sop-change-review.csv. Each process owner checks the actual authorized tenant using a synthetic record before approving a revised SOP; preserve old version and sign-off. Expected output: Source-checked sop-change-review.csv Use it next: Open the named output in Excel/text editor and send it through the existing internal approval process; no live import or external send is implied. Check: Acceptance case (proposed, not run): A Clio Grow announcement does not prove a Clio Manage SOP changed; staged rollout remains unverified. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://www.clio.com/features/whats-new/ https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint STEP 6: Approve the internal next action Tool: Responsible human owner Open: Existing internal work queue / approved source system Record the reviewer, decision and unresolved blockers. Each process owner checks the actual authorized tenant using a synthetic record before approving a revised SOP; preserve old version and sign-off. Expected output: Approved internal review record or explicit blocked status Use it next: An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase. Check: Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://www.clio.com/features/whats-new/ https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint ACCOUNT AND SOURCE CHECKS STILL NEEDED - Official public release notes alone cannot establish exact availability, entitlement or UI in a specific tenant. EXPECTED SYNTHETIC CHECK (NOT RUN) A Clio Grow announcement does not prove a Clio Manage SOP changed; staged rollout remains unverified. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.