Quotas & Limits owns the measured quota summary and the tenant and throttle drill-ins. It offers no quota forecast, alert configuration or report export (withdrawn, see below).
Health & SLO owns service detail and incident history; service tiles must not deep-link into stale platform paths.
Cross-shell actions should stay contextual:
quota tenant detail can hand off into Evidence > Audit Log
Added canonical route helpers and alias coverage for quota, health, and AOC old bookmarks.
Rewired the Operations navigation tree so AOC no longer points at stale /ops/aoc paths.
Made quota dashboard category chips drive real history and forecast loading through the URL (withdrawn 2026-10-09 with the history and forecast reads; see Withdrawn).
Repaired quota forecast, alert, tenant-detail, and report flows so they use canonical routes and usable local export or payload generation instead of dead links or console placeholders (the forecast, alert and report flows were withdrawn 2026-10-09; see Withdrawn).
Repaired health breadcrumbs and service drill-ins to stay inside the mounted Health & SLO subtree.
Repaired AOC provenance navigation and made guard-violation filters affect the actual request payload.
2026-10-09 (SPRINT_20261007_017 CCP-037): /ops/operations/quotas/forecast, /ops/operations/quotas/reports and /ops/operations/quotas/alerts resolve to the normal not-found page; the generic /ops/quotas/:page and /platform/ops/quotas/:page redirects still forward to those paths and therefore end there too. Platform answers the Console’s quota forecast and alert-configuration reads 503 and its report routes 404 in every environment, and the alert POST is withdrawn: no owner publishes a forecast, a report export or a durable alert configuration. The pages showed a “0 Healthy” forecast count and a regression methodology after the failed read, invented alert thresholds and channels with a Save that could not store, and a report generator whose request could only fail. The dashboard’s alert-configuration and report-export buttons, its forecast panel and its consumption-trend, licence and KPI panels are removed with them. Since this change the dashboard shows the metered owner summary (used amount, unit, period, source and measurement time for the signed-in tenant; an operator ceiling and the remaining amount only when one is configured) and states what no owner publishes. Each retained panel reads its own source, and a failed read stays visible as unavailable rather than empty or zero. The tenant and throttle drill-ins are retained: the 2026-10-09 live recheck found that both open their own pages. Their reads (tenant list, tenant breakdown, rate-limit status and violations) have no owner source and Platform answers them 503 in every environment, so the tenant list shows “Tenant usage unavailable” with no status counts and no CSV export, and the tenant detail shows “Tenant quota details unavailable” instead of “Tenant not found”. The dashboard’s empty throttle answer reads “No throttle events reported”; the read requests no time window. The sources are frozen under src/__Obsoleted/Web/StellaOps.Web/CCP-037/.
2026-10-08 (SPRINT_20261007_002 CCP-004): the whole AOC Compliance family is withdrawn. /ops/operations/aoc, /ops/operations/aoc/violations and /ops/operations/aoc/ingestion resolve to the normal not-found page, and so do the legacy /ops/aoc and /ops/aoc/:page bookmarks (their redirects are removed). The /platform/ops/aoc and /platform-ops/aoc redirects are removed as well; those legacy prefixes fall through to their generic Jobs & Queues landing like any other unknown legacy path. The pages rendered the fixed values of Platform’s Development/testing /api/v1/aoc reads (23 guard violations at 0.18%, 99.1% provenance completeness, P95 301 ms, Docker Hub 5.2/min, GitHub Packages 3.7/min, 18% errors, three fixed violation rows, timestamps computed back from the request time). No service owns AOC metrics, guard violations or ingestion flow, so the Platform reads are withdrawn too and no operation on the family survives; an empty page is not kept. There was no sidebar entry; the helper-tip entry for the family is removed.
2026-10-08 (SPRINT_20261007_002 CCP-005): /ops/operations/aoc/provenance (Provenance Validator) and /ops/operations/aoc/report (Compliance Report) resolve to the normal not-found page. The generic /ops/aoc/:page and /platform-ops/aoc/:page redirects forwarded to these paths until CCP-004 removed them (see the CCP-004 entry above). The dashboard’s Provenance Chain Validator panel and “Export Report” link and the per-row Retry controls on the dashboard and the violations list are removed. The Platform actions behind them (the provenance/validate, compliance/reports, compliance/violations/{violationId}/retry and verify handlers of the /api/v1/aoc group) returned a fixed complete chain, fixed totals and success without queued work, and no service owns those operations. The remaining dashboard, violations and ingestion reads are contained by CCP-004.
measured quota usage and the tenant and throttle drill-ins
service-level health drill-ins and incident export
Why:
these are not abandoned product ideas; they are real operator surfaces that had route and workflow drift after the Operations shell consolidation
current source state (2026-10-09): only the measured usage has an owner read (GET /api/v1/platform/quotas/summary). The tenant and throttle drill-ins resolve to their own pages, but their reads answer 503 in every environment and the pages show them as unavailable; whether to withdraw them or rebind them to an owner read is an open decision.
