SYNTHETIC EXAMPLE — NOT CUSTOMER WORK
Fictional report: Northstar Home monthly performance note

Purpose
Show the structure of a ReportPatch patch and acceptance plan. All names, totals, findings, and decisions below are synthetic.

1. Source reconciliation
Patch: Tie the report's $4,800 spend and 96 platform-reported conversions to independent Google Ads and Meta Ads exports.
Accept when: Each source total matches the report slice, combined spend variance is $0.00, and any conversion variance is explained in writing.

2. Metric definitions
Patch: Name the exact conversion actions included by each platform and state that cross-platform totals are not deduplicated unique leads.
Accept when: The definitions approver confirms the included actions and the output says "platform-reported conversions."

3. Date windows
Patch: Record the timezone, inclusive start date, inclusive end date, and comparison-period dates for every source.
Accept when: Both exports and the report use the approved September 2026 window with no unstated boundary difference.

4. Claim boundary
Patch: Separate delivery metrics from lead-quality and revenue conclusions.
Accept when: The report makes no unique-lead, revenue, attribution, or causal claim without approved CRM evidence.

Definitions approver in this synthetic example: Analytics lead
Decision: ACCEPT only after all four gates pass; otherwise REVISE or HOLD the report.