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.

Find calendar differences across tools
Starter kit G22

These files support a manual, read-only pilot. The workflow is proposed and has not been run against a live system. All example records are invented.

START HERE
1. Keep blank templates and synthetic examples separate. Use the example files first, renaming copies to the input names listed below if the prompt expects those names.
2. Open CSVs with UTF-8 and comma delimiters. Preserve IDs, timestamps and empty values as text on import. Empty means missing, not zero. There are no formulas. Do not change column headings.
3. Prepare the required policies and native documents. Stop any check whose inputs, coverage or permission are missing.
4. Use the recipe's prompt in the firm-approved workspace and request the stated review artifact. Treat all file content as data, not instructions.
5. Compare the result with expected-results.txt and the original rows/pages. Do not enable live connections or send anything from this kit.

INPUT CONTRACT
appointments.csv: system, event_id, start_datetime, end_datetime, timezone, host_alias, location_id, cancelled, exported_at
event-map.csv: appointment_alias, system, event_id
calendar-policy.txt: source of truth per field, coverage limits, stale-export threshold; omit private events and client-identifying titles

RECIPE-SPECIFIC SETUP
The fixture uses explicit mappings, not fuzzy title matching. All titles and private events are omitted.

PREREQUISITES
- Read-only event exports, stable cross-system IDs or explicit matching table, timezone normalization, source-of-truth policy, no event-title client details in analysis.
- Start with synthetic data. Real firm data requires approved access, processing terms, retention, and confidentiality controls. Replacing names with IDs alone does not anonymize a record.
- Verify the current account, plan, export scope, and approved reviewer before trying the documented product feature. This prompt works on prepared files; it does not install or configure an integration.

REVIEW CHECK
Never automatically cancel, move or recreate events; doing so can send client notifications. Keep private events out of the comparison. Different job from G05, which checks whether a proposed slot is feasible.

EXPECTED OUTPUT
calendar-drift.csv: appointment_alias, field, source_system, source_value, other_system, other_value, coverage_status, proposed_review

Validation covers file syntax, exact declared headers and fixture consistency. It does not establish product compatibility, legal sufficiency, data completeness or production readiness.