Build a source-backed event briefing

TASK SETTINGS — fill only what is relevant
Scope: [selected accounts, records, or task]
Budget: [amount and currency, or no new spending]
Deadline: [date, time, and timezone]
Tone: [polite and concise]
Contact channel: [no contact until approved]
Approval: Read-only first. Ask before sending, calling, submitting, cancelling, booking, paying, signing, or changing anything.

Prepare a concise briefing before I attend an event.

Use only the accounts and materials I authorize. Start with: the event, official agenda, my interests, sessions I am considering and time constraints.

Verify the date, venue, schedule changes, accessibility information and registration conditions. Research session topics from the organizers and speakers’ primary material without inferring private information. Identify useful questions and conflicting sessions. Separate confirmed logistics from optional networking suggestions.

Work read-only and prepare drafts first. Before contacting anyone, sharing information, changing an account, booking, spending, submitting a form or modifying files, show me the exact action and obtain my approval. Do not register, contact attendees, scrape private attendee lists or buy tickets.

Verify that your tools actually support the requested work. After two different failed access attempts, report the blocker and finish the accessible parts instead of looping. Never invent an action, source, availability or confirmation.

Return: a one-page brief, suggested agenda, practical logistics, source links and questions to bring. Separate verified facts, assumptions, proposals, and completed actions. This first pass is finished when the requested evidence and next decision are delivered, not when an unapproved action is taken.