Workspace Applications Read
What This Service Is For
This read supplies the administrator with the applications a workspace can use and a readable explanation when one is unavailable. Configuration presents the response without editing controls.
Boundary
The route belongs to the workspace API, and licensing owns its computation and storage. It is specified here provisionally because this module carries the administrator-facing rules. The recorded ownership question recommends Operations as the eventual home.
Operations in Words
The operation returns application keys and names, availability, licensing dates and operational state. Licensing is reduced to licensed or not licensed, and withholding is reported as not licensed. The caller needs the workspace-applications read permission and reach over the requested workspace. Out-of-reach workspaces return not found. The operation is excluded from configurable intake because it captures no business data.
Events and Jobs
The route has no event, scheduled job or model invocation. Licensing synchronization and reconciliation belong to Operations.
Consistency Guarantees
Every request reads licensing data without a route cache. Availability and registry reads run independently rather than in a declared common transaction. The route checks reach itself and does not apply the path-workspace availability gate. The menu uses a separate Security snapshot, so the two presentations can disagree during cache and refresh delays.