Reconcile new court-docket entries with the matter register 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 - Named example is CASB CM/ECF; other courts can have different menus and report behavior. - If the case, fee authority or complete report is missing, acquisition is blocked; work only on existing authorized snapshots. No legal deadlines are calculated. MAP THE ACTUAL SOURCE TO THE REVIEW INPUT Court plus displayed case number plus docket entry number → exact composite key; Date Filed → filed_date, exact Docket Text → docket_text, entry/document link → document_ref, actual retrieval timestamp → snapshot_at. No entry number means no fabricated key: preserve source row locator and mark ambiguous. Existing matter-register fields remain separate. Strip names/case text from AI unless expressly approved; use aliases and minimal neutral text. INPUTS THE ASSISTANT MAY READ docket.csv; register.csv; snapshot-scope.txt; docket-snapshot/; 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: docket.csv type: csv headers: - court_id - case_id - entry_id - filed_date - docket_text - document_ref - snapshot_at required: True templateFilename: native-docket-template.csv existingKitFiles: - docket.template.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: docket.csv compatibleWithoutMapping: True - name: register.csv type: csv headers: - court_id - case_id - entry_id - recorded_text - register_id - owner_id - review_status required: True templateFilename: native-register-template.csv existingKitFiles: - register.template.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: register.csv compatibleWithoutMapping: True - name: snapshot-scope.txt type: text requiredSections: - court_id and case_id; named court/portal/version - range_start and range_end; filed-versus-entered date basis; UTC/local timezone - all_pages_exported true/false/unknown; page/item count and captured count - exported_at and snapshot_at; full source report token; text/HTML format - restricted/unavailable entries or attachments; row-key gaps; prior/current snapshot references - operator and completeness-review decision required: True templateFilename: native-snapshot-scope-template.txt existingKitFiles: - coverage.template.json - coverage.schema.json compatibility: Legacy coverage.json supplies court_id,case_id,range_start,range_end,all_pages_exported,exported_at only. Transcribe those exact values into this text companion, then add date basis, timezone, pages/counts, source report and gaps. Keep legacy JSON if desired, but it alone does not satisfy the native scope contract. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete. inputName: snapshot-scope.txt sections: - court_id and case_id; named court/portal/version - range_start and range_end; filed-versus-entered date basis; UTC/local timezone - all_pages_exported true/false/unknown; page/item count and captured count - exported_at and snapshot_at; full source report token; text/HTML format - restricted/unavailable entries or attachments; row-key gaps; prior/current snapshot references - operator and completeness-review decision compatibleWithoutMapping: False - name: docket-snapshot/ type: source-bundle required: True templateFilename: None requiredContents: Actual complete in-scope approved/minimized report with row references; restricted original retained outside AI 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: docket-snapshot/ 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: - coverage.json is optional legacy packaging after its values are reconciled to snapshot-scope.txt; the companion is required for the native route. A false or unknown all_pages_exported never becomes complete. 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: - docket.template.csv nativeInput: docket.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: - register.template.csv nativeInput: register.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: - coverage.template.json - coverage.schema.json nativeInput: snapshot-scope.txt mapping: Legacy coverage.json supplies court_id,case_id,range_start,range_end,all_pages_exported,exported_at only. Transcribe those exact values into this text companion, then add date basis, timezone, pages/counts, source report and gaps. Keep legacy JSON if desired, but it alone does not satisfy the native scope contract. compatibleWithoutMapping: False additionalEvidence: - docket-snapshot/ - 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. docket.csv: native-docket-template.csv register.csv: native-register-template.csv snapshot-scope.txt: native-snapshot-scope-template.txt Supply actual evidence: docket-snapshot/ Actual complete in-scope approved/minimized report with row references; restricted original retained outside AI 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: Obtain a complete scoped docket snapshot Tool: U.S. Bankruptcy Court, Southern District of California CM/ECF/PACER Open: Reports > Docket Report; case number and filed/entered date or document range Use an existing authorized downloaded docket report, or have the authorized court-records operator acquire one under approved PACER charges. The named court guide supports Docket Report with case/range criteria. Save the full resulting report and retrieval/billing receipt; record selected date basis, scope and every displayed entry. Do not open paid documents without authority. No login or purchase is performed here. The named court guide supports HTML or Text format and Run report; retain the complete rendered/text result locally with its capture manifest, not just a screenshot of the first entries. Expected output: Named-court docket snapshot with case and entry references Use it next: Compare to the approved matter register in the restricted workspace. Check: An email notice or search preview is not a complete docket. Document links, attachments and restricted entries may need separate authorized review; fee-bearing access requires approval. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://racer.casb.uscourts.gov/ecf_train/ecf_videos/manual/Reports%2CUtilities%2CPACER/reports-docketreport.htm https://pacer.uscourts.gov/sites/default/files/files/PACER-User-Manual_2025.pdf https://pacer.uscourts.gov/ 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: Court plus displayed case number plus docket entry number → exact composite key; Date Filed → filed_date, exact Docket Text → docket_text, entry/document link → document_ref, actual retrieval timestamp → snapshot_at. No entry number means no fabricated key: preserve source row locator and mark ambiguous. Existing matter-register fields remain separate. Strip names/case text from AI unless expressly approved; use aliases and minimal neutral text. 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 docket.csv; register.csv; snapshot-scope.txt; docket-snapshot/; 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://racer.casb.uscourts.gov/ecf_train/ecf_videos/manual/Reports%2CUtilities%2CPACER/reports-docketreport.htm https://pacer.uscourts.gov/sites/default/files/files/PACER-User-Manual_2025.pdf https://pacer.uscourts.gov/ 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 Compare captured docket entries and the matter register by exact court_id + case_id + entry_id. Report new entries, text changes, missing document references, unmatched register rows and capture gaps with source row references. Retain filed date and snapshot time exactly; do not derive a due date or legal effect from docket text. A restricted or unavailable entry is a coverage gap. Do not download documents, calendar events, update records or represent this as a complete court audit without verified scope. Expected output: docket-register-exceptions.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 docket-register-exceptions.csv. Responsible lawyer reviews every new or changed source entry and directs any register update or separate calendaring process. Expected output: Source-checked docket-register-exceptions.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): Changed docket text under the same key becomes a discrepancy, while a matching entry number in another court remains distinct. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://racer.casb.uscourts.gov/ecf_train/ecf_videos/manual/Reports%2CUtilities%2CPACER/reports-docketreport.htm https://pacer.uscourts.gov/sites/default/files/files/PACER-User-Manual_2025.pdf https://pacer.uscourts.gov/ 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. Responsible lawyer reviews every new or changed source entry and directs any register update or separate calendaring process. 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://racer.casb.uscourts.gov/ecf_train/ecf_videos/manual/Reports%2CUtilities%2CPACER/reports-docketreport.htm https://pacer.uscourts.gov/sites/default/files/files/PACER-User-Manual_2025.pdf https://pacer.uscourts.gov/ ACCOUNT AND SOURCE CHECKS STILL NEEDED - Named example is CASB CM/ECF; other courts can have different menus and report behavior. - If the case, fee authority or complete report is missing, acquisition is blocked; work only on existing authorized snapshots. No legal deadlines are calculated. EXPECTED SYNTHETIC CHECK (NOT RUN) Changed docket text under the same key becomes a discrepancy, while a matching entry number in another court remains distinct. 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.