Build the compute catalogue screen: what the grid runs
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
1. What
The system administrator has no screen for what the compute grid may run. The journey Keep what the grid runs reads the apps, their versions, the platforms and packages, and the concurrency policy. A super administrator writes the catalogue. No BFF route serves a compute screen. The system home shows it as an upcoming card.
2. Why
The read subjects exist: compute.v1.apps.list, .app_versions.list,
.app_version_platforms.list, .platforms.list and
reporting.v1.concurrency_policies.list. The write subjects exist too, gated by
compute::apps:write and its siblings. The journey names what is missing: no
aggregate of the builds each job pinned, no cap row to compare in-flight work
against, and no browser upload path, because compute publish-package is
shell-only.
The first slice is the read-only catalogue for any signed-in person, as one hand-written BFF route on the journey runtime. The write controls follow, shown only to the super administrator.