Workspace

Calendar

Plan local work today with a clean boundary for secure sync tomorrow.

Local calendar model

Calendar events use a provider-neutral domain model. The UI should not depend on one vendor's response shape, authentication method, or identifier scheme.

Stable local identifiers
Provider metadata kept at the boundary
Explicit timezone handling
Conflict-aware updates

Future sync boundary

Remote calendar adapters will authenticate outside presentation components, normalize provider events, and hand them to the same repository interface used by local data.

Tokens belong in secure platform storage or a trusted server-side broker-never in browser storage or rendered application state.