Reading Calendars¶
Source: hooks/ways/ea/calendar/reading/reading.md
Frontmatter
| Field | Value |
|---|---|
description |
reading a colleague's calendar in a shared workspace, listing the meetings two people both attended, and telling an accepted invite from attendance and an untitled entry from a meeting |
vocabulary |
colleague coworker teammate both shared meetings attendee address private untitled attended attendance accepted declined rsvp organizer happened joined did i go |
refire |
0.15 |
scope |
agent, subagent |
Other people's calendars¶
- In a shared workspace, such as one Google Workspace or Microsoft 365 tenant, you can often read a colleague's calendar by using their email address as the calendar ID. Use it to see their day, find open slots, check whether an invite already exists, or review past meetings.
- Event search often matches attendee addresses as well as titles. Open one person's calendar and search for a second person's address to list the meetings they share.
- Private events show only as busy. Do not guess what they are.
Reading the record carefully¶
- An untitled busy block is a hold, not a meeting. Do not report it as one.
- An invite, or even an acceptance, does not prove the user attended. Confirm attendance from a transcript, notes, or a follow-up before you treat a meeting as held.
- An RSVP sends a message to the organizer. Treat it like any other send, and send none while reading.
See Also¶
- calendar(ea) — parent: creating and changing events
- comms/recap/transcripts(ea) — transcripts that show whether a meeting happened
- intelligence(ea) — meeting prep built on the calendar