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.

Check rooms and attorneys before booking
Starter kit G05

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
availability.csv: person_alias, location_id, start_datetime, end_datetime, timezone, exported_at
rooms.csv: room_id, location_id, start_datetime, end_datetime, acceptance_status, exported_at
booking-rules.csv: appointment_type, duration_minutes, buffer_before_minutes, buffer_after_minutes, required_roles, allowed_location_ids

RECIPE-SPECIFIC SETUP
Test context: as-of 2026-10-15T09:00:00Z; exports current for this fixture only. Test three separate candidate slots on 2026-10-16, 10:00–10:30 UTC at LOC1/LOC2/LOC3. Roster: ATT1 is attorney at LOC1; ATT2 at LOC2; ATT3 at LOC3. All example calendars cover 09:00–12:00 with no other bookings except ROOM2. Free gaps are usable only under this explicit complete-coverage assertion. ROOM1 acceptance is pending. ROOM3 test-candidate acceptance is supplied. Real exports require verified freshness, full buffer coverage and native room acceptance; an export never confirms a new booking.

PREREQUISITES
- Microsoft 365/Exchange room mailboxes, maintained attorney-location roster, calendar access and firm-approved buffers. A coordinator can perform a manual approval step; custom orchestration needs separate technical proof.
- 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
Do not assume an event written directly into a room calendar enforces booking policy. Verify concurrent booking/race conditions in a synthetic test; no confidential calendar titles; no automatic security/admin settings changes.

EXPECTED OUTPUT
slot-review.csv: slot_id, start_datetime, end_datetime, timezone, location_id, person_aliases, room_id, status, evidence_rows, review_reason

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