Find procedures affected by software changes
manifest.txt
BLANK INPUT: complete from acquired, approved evidence

New companion capture/review record. Staff supplies observed or approved values; unknown is explicit.

REQUIRED SECTIONS
recipe_id; approved reviewer and scope
[Complete from the source. If unavailable, write unknown and explain the gap.]

actual source IDs and safe original-file tokens; native headers and source-to-analysis field map
[Complete from the source. If unavailable, write unknown and explain the gap.]

capture time/timezone; date basis; filters; property/court/provider; pagination/row counts and known exclusions
[Complete from the source. If unavailable, write unknown and explain the gap.]

AI input approval and minimization check; originals and alias keys held outside AI
[Complete from the source. If unavailable, write unknown and explain the gap.]

unknowns; completeness statement; manual transcription/checker where used
[Complete from the source. If unavailable, write unknown and explain the gap.]

IF EVIDENCE IS MISSING
Stop the dependent comparison or mark affected scope explicitly incomplete.

VALIDATION RULES
- 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.

Read START-HERE.txt and NATIVE-INPUT-MAPPING.txt for source acquisition, privacy gates and the exact handoff. Include this completed input wherever the prompt expects it; a file that was not loaded or pasted is not AI-visible.