Dates Follow the Workspace Calendar

Context

Dates describe business days rather than universal instants. Inclusive ends make a relationship effective for its whole final workspace day, while reads compute its current classification.

Decision

Relationship and role dates use the workspace calendar with inclusive end days; reads derive future, current and past classification; eligible roles and compliance effects follow saves or reconciliation rather than early assignment.

Alternatives Considered

Use the browser or server date. Near midnight those clocks can classify a relationship differently from the workspace. The recorded timezone decision rejects that disagreement.

Persist a classification and rewrite it nightly. A stored classification can be stale between the boundary and maintenance, and would require needless per-record nightly updates.

Consequences

Pending effects are separate from that classification. Roles, default links and compliance can await a scheduled pass, an unlocked record or a later save. Deployment defaults and backlog limits must therefore remain visible when describing boundary behavior.

Calendar classification changes at the workspace day boundary without a write. Effects still need bounded reconciliation or save-time work, and the full scheduled date pass is disabled by default in production.