Empty slots are not availability

A gap between events is a fact about a calendar. Availability is a judgment about whether a meeting belongs there.

Someone may need that gap for preparation, travel, or uninterrupted work. A team in another timezone may read the same instant as the end of their day. A scheduling process that ignores those differences can produce a technically possible meeting that nobody welcomes.

Ask what the gap is for

Before proposing a time, consider:

• Whether it falls inside the attendees’ working hours.
• Whether another meeting leaves enough transition time.
• Whether the day already has a heavy meeting load.
• Whether the gap is the only longer stretch for individual work.

These can be team conventions before they become software rules. Write them down and check them when arranging a meeting.

What a future scheduler could do

Instead of simply returning empty slots, a scheduler could rank a few options and explain the tradeoffs. An option might work for everyone’s hours but interrupt a focus block; another could preserve that block but move the meeting to tomorrow.

That is a design direction for AI scheduling. It is not how mmddyy v1 selects times: the current app does not perform availability searches or enforce working hours, buffers, meeting limits, or focus rules.

What you can do in mmddyy today

Create a personal or team calendar, enter the time people have agreed on, and share access with viewer or editor invite links. You can add a regular event for writing or other work, but it is an ordinary event. The app does not automatically defend it against other events.

Viewers see event details on a shared calendar. If an event is sensitive, keep it on an unshared calendar rather than assuming a free/busy-only mode exists.

Read how it works for the current workflow and the documentation for its limits. A useful roadmap should help explain an idea without making today’s calendar sound more automatic than it is.