zara-calendar: calendar search, scheduling and conflict reasoning #10

New issue

Closed

opened 2026-08-31 18:43:13 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-31 18:43:13 +00:00

(Migrated from github.com)

Plugin

zara-calendar

Goal

Give Zara a provider-neutral calendar domain for answering “what’s next?”, finding time, creating/rescheduling events and reasoning about conflicts.

Capabilities

list/search events by time/text/calendar;
inspect event details and attendees;
free/busy queries;
create/update/delete events through explicit mutation tools;
recurring event handling;
reminders/alarms metadata;
conflict detection and scheduling suggestions;
expose upcoming-event context to Zara when requested.

Architecture

Use provider adapters so Google Calendar, CalDAV and other backends can share one domain model. Keep provider auth outside committed plugin data.

Optionally use zara-expert rules for constraints such as working hours, buffers, priorities and conflict policies.

Safety

clearly separate suggestions from calendar writes;
never silently invite/remove attendees;
preserve timezone information explicitly;
mutations return provider IDs/version/evidence;
bounded search windows and result counts.

Acceptance criteria

provider-neutral event/free-busy model exists
search and upcoming-event queries work through a fake backend
create/update/delete operations are explicit and verified
timezone and recurrence handling are tested
conflict detection can explain why a candidate time fails
README documents provider adapter/auth contract
registry validation, plugin tests and nix flake check pass

## Plugin `zara-calendar` ## Goal Give Zara a provider-neutral calendar domain for answering “what’s next?”, finding time, creating/rescheduling events and reasoning about conflicts. ## Capabilities - list/search events by time/text/calendar; - inspect event details and attendees; - free/busy queries; - create/update/delete events through explicit mutation tools; - recurring event handling; - reminders/alarms metadata; - conflict detection and scheduling suggestions; - expose upcoming-event context to Zara when requested. ## Architecture Use provider adapters so Google Calendar, CalDAV and other backends can share one domain model. Keep provider auth outside committed plugin data. Optionally use `zara-expert` rules for constraints such as working hours, buffers, priorities and conflict policies. ## Safety - clearly separate suggestions from calendar writes; - never silently invite/remove attendees; - preserve timezone information explicitly; - mutations return provider IDs/version/evidence; - bounded search windows and result counts. ## Acceptance criteria - [ ] provider-neutral event/free-busy model exists - [ ] search and upcoming-event queries work through a fake backend - [ ] create/update/delete operations are explicit and verified - [ ] timezone and recurrence handling are tested - [ ] conflict detection can explain why a candidate time fails - [ ] README documents provider adapter/auth contract - [ ] registry validation, plugin tests and `nix flake check` pass