data/sessions/calendar-create-event/memory.md

# Memory: calendar-create-event

## Overview

Create a timed calendar event by placing it directly on the calendar grid. Use this when
an event has to be created at a visible position in the week and no shell is available or
wanted — the time comes from where the click lands rather than from a typed value. The
route launches the application through the system search field, switches to the week view,
double-clicks the target hour slot, types the title and commits it with Return. The
recorded trace produces `Standup` at 09:00–10:00 on the chosen weekday.

## Prerequisites

- A desktop environment with a calendar application, reachable either through its own
  window or through a scripting interface.
- The event's title, start time and duration decided in advance.
- The target calendar known. A window-driven route creates the event in whichever
  calendar is currently selected; a scripted one names the calendar and fails if that
  name does not exist rather than falling back to a default. Read the name from the
  application rather than assuming it.
- A clear intent about the date. Creating an event "today" is repeatable and is wrong
  whenever a specific date was meant.
- Authority to grant the permissions a first run requests. A scripted route needs two
  separate grants — control of the application, and access to its data — and both are
  required before the event exists.
- An understanding that those grants persist. A denial is remembered as firmly as an
  approval and is not asked for again.

## Steps

### Step 1 — Press: Cmd+Space

The task is to put a 9 AM event called `Standup` on Thursday in the calendar, so Calendar has to be running first. The desktop is bare with no window open; press ⌘Space (Cmd+Space) to open Spotlight, which finds an application by name without needing its Dock position.

![Step 1](vision/frames/step_0001_20260723_083838_at.webp)

### Step 2 — Type: Calendar

Type `Calendar` to search for the application. Spotlight narrows as the characters arrive and promotes its best match to the top of the list, which is what Return will act on.

![Step 2](vision/frames/step_0002_20260723_083845_at.webp)

### Step 3 — Press: Enter

After typing `Calendar` Press Return to launch the highlighted top hit.

![Step 3](vision/frames/step_0003_20260723_083850_at.webp)

### Step 4 — Move-cursor at (642, 46)

Calendar opens on **Month** view, which shows whole days as boxes with no hour grid, so a specific 9 AM slot cannot be picked in it — the view has to change first. Move the cursor onto the `Week` tab in the view switcher at the top of the window. Moving to the target and clicking as a separate step is more dependable here than a combined move-and-click, which sometimes reaches the position without the click registering.

![Step 4](vision/frames/step_0004_20260723_083901_at.webp)

### Step 5 — Left-click at (642, 46)

Move the cursor and Left-click the `Week` tab to switch views. Week view draws each day as a column against an hour grid, which is what makes a particular time of day clickable. Calendar does not remember this choice between launches — it opens on Month every time — so this is a real step of the task rather than incidental setup.

![Step 5](vision/frames/step_0005_20260723_083911_at.webp)

### Step 6 — Move-cursor at (815, 230)

The week now runs `Sun 19` to `Sat 25` with today, Thu 23, marked in red. Move the cursor into the Thursday column at the 9 AM row — the point just below the `9 AM` line and above `10 AM`. Getting the column right matters as much as the hour: the same height in a neighbouring column would create the event on the wrong day.

![Step 6](vision/frames/step_0006_20260723_083923_at.webp)

### Step 7 — Double-click at (815, 230)

Move the cursor and Double-click the empty 9 AM slot to create an event there. Calendar makes a default one-hour event from the slot that was clicked — `23 Jul 2026 9 AM to 10 AM` — and opens its inspector with the title `New Event` selected and the caret in it. The times come from where the double-click landed, not from anything typed, so the slot is what sets the schedule.

![Step 7](vision/frames/step_0007_20260723_083939_at.webp)

### Step 8 — Type: Standup

Type `Standup` to name the event. The caret is already in the inspector's title field, so the text replaces the placeholder `New Event` without anything having to be clicked first.

![Step 8](vision/frames/step_0008_20260723_083951_at.webp)

### Step 9 — Press: Enter

After typing `Standup` Press Return to commit the title and dismiss the inspector. Until this point the event exists only as an open editor; Return is what writes it to the calendar. The block in the grid changes from `New Event` to `Standup`, which is the confirmation that the name was stored.

![Step 9](vision/frames/step_0009_20260723_084012_at.webp)

### Step 10 — Press: Cmd+Q

The event is committed and Calendar saves as it goes, so nothing else needs saving — press ⌘Q (Cmd+Q) to quit the application. Unlike closing a window, quitting ends the process, which leaves the machine in the state the task started from.

![Step 10](vision/frames/step_0010_20260723_084026_at.webp)

## Notes & Edge Cases

1. The application opens on a view that cannot express the task. Month view shows whole days with no hour grid, so a particular time of day is not clickable until the view changes — switching it is a real step of the work rather than incidental setup.
2. The view is not remembered between launches. It opens on the same view every time, so the switch has to be repeated on every run and cannot be treated as machine state that persists.
3. The double-click is what sets the schedule, not anything typed. A default one-hour event is created from the slot that was clicked, so the column decides the day and the height decides the hour — the same height one column over creates the event on the wrong day with everything else looking right.
4. The title field already holds the caret and a selected placeholder when the inspector opens, so typing replaces it without anything being clicked first. Clicking into the field can deselect the placeholder and leave the typed text joined onto it.
5. The event exists only as an open editor until the title is committed. The confirming key is what writes it to the calendar, and the block in the grid changing from the placeholder to the typed name is the evidence it was stored.
6. The event is created relative to what the grid is showing. Running the same steps in a different week produces an event in that week, which is what makes the route repeatable and also what makes it wrong when a specific date was intended — read the dates in the column headers rather than trusting the position.
7. Quitting ends the process where closing the window would not. The application saves as it goes, so the quit commits nothing; it only returns the machine to the state the task started from.
8. Move to the target and click as separate actions; a combined move-and-click sometimes reaches the position without the click registering.