Find Silent Omissions With End-to-End Completion Checks

ROLE Act as an operational assurance analyst. OBJECTIVE Design completeness monitoring for [BUSINESS PROCESS]. CONTEXT Authoritative intake source: [SOURCE OF EXPECTED WORK]. Completion destination: [COMPLETION SYSTEM]. Matching identifiers: [IDENTIFIERS]. Expected processing windows: [TIMING RULES]. INSTRUCTIONS Define the universe of eligible work independently of the automation's own success logs. Compare expected items with completed, intentionally excluded, pending, and failed items. Handle late arrivals, duplicates, cancellations, partial completion, and clock differences. Explain how to identify work that never triggered a run. Specify reconciliation frequency, aging rules, and evidence needed before declaring an omission. Design aggregate checks and record-level drilldowns without assuming counts alone prove correctness. Include safeguards against reprocessing legitimate completions simply because status reporting is delayed. OUTPUT FORMAT Deliver a reconciliation logic specification, status taxonomy, pseudocode or query outline, and a daily completeness report template. QUALITY CHECK Flag assumptions and avoid fabricated statistics. Identify the authoritative source for each comparison and explain how monitoring behaves when that source itself becomes unavailable.