Confirmation and Safety
Calendaria is designed around a simple rule: reads can be fast, writes must be confirmed.
Read operations
Read-only commands execute immediately:
- listing events
- checking what is on a day
- looking at a time window
- answering status-style questions
Write operations
Calendar mutations create a pending action first:
- create an event
- move or edit an event
- delete an event
- invite attendees
- change preferences
The bot shows a human-readable summary. The real Google Calendar API call happens only after you confirm.
Why this exists
Natural language can be ambiguous. A model can misread a time, choose the wrong event, or infer a parameter you did not intend. Confirmation keeps the speed of natural language while protecting the real calendar.
Conflict warnings
When Calendaria detects conflicts for a create or move request, it warns you and may suggest alternative slots. Choosing an alternative slot is treated as explicit confirmation for that slot.