The problem is not “a second Sigma.” The problem is a 60-second ops wall: five headline
numbers (registered apps, active Kronos jobs, open SRM, NLG pool, token cost), a live grid that
polls each blueprint’s /health, three charts, and a 20-row activity feed from SHL
milestones and Herald. Nexus owns tables: []. Metrics prefer the Sigma API
and fall back to Kronos/GHT/SRM/NLG/TKN tables. Login on /nexus/app is Flask-Login,
no SWIP callback inside this blueprint. JSON uses mcp_or_login. No Nexus env vars. README still
mentions Telegram helpers — tokens retired. This is read-only: you do not mute alerts or edit
jobs here. That is Herald and Kronos.
If Sigma is down, fallback SQL still tries. If a /health 404s, the grid should show it — not hide it.
Zeros mean empty tables or Sigma fallback 0. Not an outage Lottie.
A red cell is a failed /health, not a designed alert.
Sigma: 19 queries + threshold rules. Nexus: no tables, prefers Sigma API.
Click through. This page is a map, not a wrench.
Will not store a parallel metric warehouse. Landing does not poll 50 /healths for strangers.
Engineers with a MelTuc session. Not a statuspage.io for customers.
No invented incident commander.
Login for /nexus/app. This page does not live-poll the fleet for the public.
Open NexusRequires a MelTuc account. Create one free.
Platform Operations Center — real-time command dashboard aggregating health and activity. Health stays cheap. If this page disagrees with the signed-in app, trust the app — the product contract and tests enforce that rule.