Request-Specific Availability

Context

A workspace can be closed to its customers while authorized staff still inspect it. Loading adds a route exception, so availability depends on more than a stored boolean.

Decision

Compute request availability from workspace lifecycle, business standing and caller-route context, using directly read facts with a thirty-second process cache.

Alternatives Considered

Publish lifecycle changes as events for each service to apply: Event delivery would introduce another source of delay and ordering uncertainty. Call Platform on every request: A synchronous service call would add a network dependency to every request. Store availability as a field: One stored availability value cannot express the caller and route exceptions.

Consequences

Lifecycle paths clear the changing process’s cache; other processes refresh after expiry. Separate application implementations can drift. The caller gets a uniform refusal while the deciding service logs the reason.