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.

Q05 - Reconcile new court-docket entries with the matter register

Status: Proposed / not tested

WHAT THIS KIT CONTAINS
Exact input scaffolds and synthetic examples for an offline pilot. Header, JSON-shape and fixture-consistency checks validate these files only; they do not test an assistant, product integration, legal decision, PDF inspection or live workflow.

PREREQUISITES
1. Staff-verified court/case identity, full relevant pagination and report cutoff/range, previous snapshot and current register; spreadsheet or approved script. Court access/fees and private NEF tokens remain outside the prompt. The data may be incomplete or delayed.

SETUP
1. Use the separate synthetic example inputs first. Fill a copy of the blank template or input checklist for your own preparation; do not mix fixture information with real records.
2. Preserve exact CSV headers. CSV templates contain only a header row. Import ID, hash, page-label and timestamp columns as text; inspect leading zeros and do not enable formulas from untrusted input.
3. Preserve JSON keys and nesting. JSON templates use blank strings, null scalars and nested placeholder rows to expose missing preparation. They are valid JSON scaffolds, deliberately incomplete. Fill all required fields and validate against the supplied schema; semantic checks in this guide remain necessary.
4. Give only the selected synthetic input sections/files and the prompt below to an existing firm-approved private workspace, or perform the clerical comparison manually. Keep expected-result notes separate from the input. For planning checklists, leave unknown requirements explicit instead of inventing them.
5. Compare the draft output with the expected fixture result. A reviewer checks original evidence and all exceptions before any separately approved action. Retain the version, scope and source references with the review.

INPUT RULES
The match key is court_id + case_id + entry_id. Preserve filed_date verbatim and compare docket_text with recorded_text exactly. all_pages_exported=false or unknown must keep coverage incomplete. Scope mismatches stay visible.

FILES
- docket.template.csv: Court entries within the staff-defined export range
- docket.example.csv: Court entries within the staff-defined export range
- register.template.csv: Existing matter register; same numeric ID in another case must not match
- register.example.csv: Existing matter register; same numeric ID in another case must not match
- coverage.template.json: Preserve nested input structure and validate supplied field types
- coverage.example.json: Preserve nested input structure and validate supplied field types
- coverage.schema.json: Preserve nested input structure and validate supplied field types

COPYABLE OFFLINE PROMPT
Compare these synthetic docket and register tables only. Validate coverage and match by exact court_id+case_id+entry_id. Return new docket entries absent from the register, duplicate IDs, same-ID changed text and unmatched register rows. Keep filed_date and source references verbatim. Missing all_pages_exported or false must yield incomplete coverage. Return IDs, exception, verbatim docket text, register_id,owner_id and document_ref. Do not interpret orders, calculate deadlines, mark an item handled, create events, fetch paid records or send notifications.

INPUTS
docket.csv = court_id,case_id,entry_id,filed_date,docket_text,document_ref,snapshot_at. register.csv = court_id,case_id,entry_id,recorded_text,register_id,owner_id,review_status. coverage.json = {court_id,case_id,range_start,range_end,all_pages_exported,exported_at}. Dates are verbatim supplied values; no deadline derivation.

OUTPUT
A queue of new, unmatched or changed docket entries for staff to review. Court dates and source references stay as recorded; no deadlines are inferred.

Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing.

EXPECTED SYNTHETIC FIXTURE RESULT
K1/11 is new/unregistered. K1/10 has changed text; retain both versions. K2/10 is an unmatched out-of-scope register row, never a match for K1/10. all_pages_exported=false makes overall coverage incomplete.

LIMITS
- Lawyer reads original orders and decides consequences/required action. Staff confirms the register actually represents the docketed document and assigns owner manually. The report never supplies legal deadlines or claims nothing was missed.
- Synthetic data only in the delivered files. No credentials, real client records, live-action scripts, API connection or Make blueprint is included.
- Real use requires firm-approved access, confidentiality, processing terms, retention, product access and reviewer authority. Pseudonymous IDs alone do not anonymize real records.