Boundaries
Cicada owns the desired-state lifecycle — declare, plan, apply, drift — and the ports everything crosses. Neighbors own theirs:
- Providers (Google Calendar API, future Teams/CalDAV) — remote truth; cicada reads/writes through
CalendarProvider, never talks HTTP itself. - Secrets —
token_env/credential names only; values resolve through env or cuora, never config. - Distribution — the
cicadacommand is a tamiasbins[]pack;tamias-driver-cicadais also thetype: cicadacontent driver. tamias owns fetch/install. - Orchestration — campaigns that schedule reconciles are peregrin's; cicada exposes bounded ops they can call.