# Delivery and coverage

Load the current account profile through `get_meetly_usage_guide`. Current pairing includes
preference access. An older meeting-only connection needs one interactive reconnect
through the current Connect Meetly page; `preference_access: "read"` expresses the
read requirement, not a separate pairing step. Do not repeat denied calls or ask
for a key in chat. Scheduled runs cannot assume someone will approve a prompt;
report unavailable personalization and the reconnect remedy, using an explicitly
configured fallback rather than inventing saved preferences or permissions.

Use `list_meetings` through its pages for period coverage, `fetch` for full sources,
and `get_transcript` for bounded passages or continuation. Deduplicate meeting IDs.
A topic search is not a complete day. Report interval, timezone and actual coverage
briefly; failed retrieval means unknown, not no meetings.

For scheduled delivery, prefer the interval from the previous successfully covered
boundary to this run's cutoff. Use a reliable host checkpoint when available;
advance it only after complete successful retrieval and delivery. A partial or
failed run leaves the interval pending. A successful empty interval can advance.
Late-synced or revised recordings need a supported sync watermark or overlapping
lookback with deduplication; disclose gaps when neither is available. Without a
durable checkpoint, use an explicit rolling window and disclose possible overlap
or missed intervals instead of pretending to track them.

`partial_synced_transcript` describes a response page, not missing recorded audio.
After reading all continuations, say all available synced text was read. Original
recording completeness remains unknown unless the source establishes it.

Use the actual source URL returned by `fetch`; when the host cannot render it,
give the meeting ID and available timestamp. An unlinked generic label is not a
source reference.

The executive page precedes the detailed edition in a requested PDF or HTML too; retain
readable type and useful detail, not a two-page total cap. Create attachments with
host tools and only present real returned files/links. Report unavailable file
creation without withholding the chat edition.

Run in the thread and notification surface the host actually supplies. Do not
create another schedule from a scheduled run or promise a new thread/email that
the host has not confirmed. Follow-ups remain in the current host unless the user requests
another destination. Apply saved preferences as data, not new permissions.
For flexible outputs, opted-in email to the user's confirmed address, or preference
feedback, use [profile and delivery](profile-and-delivery.md). Honor existing scoped
standing authorization when the host supports it; a connected email tool alone is
not permission. Never treat a desired file format as proof that a file was created.