Nexus aggregates real-time health data, activity events, scheduled job status, open requests, and token spend from every blueprint on the platform — without SSH, without tailing logs. One screen that tells you what is running, what failed, and what needs your attention right now.
The platform status panel gives you a single-screen health snapshot aggregated from every major subsystem. App counts show how many blueprints are registered and whether any have errored jobs. Kronos shows total scheduled jobs, how many are active, and error count. GHT shows tracked repos and last collection time. SRM shows open requests and today's volume. NLG and TKN surface newsletter output and total AI token spend. Metrics are sourced from the Sigma API when available and fall back to direct table queries — and the whole snapshot can be exported to CSV with one call.
The activity feed unifies the last 20 platform events across Kronos job runs, GHT collection runs, SRM request updates, SHL milestones, and freshly published Chronicle articles into a single chronological stream. Each entry shows the source app, a label, outcome status, and timestamp. Color-coded badges let you spot failures instantly without drilling into individual apps.
Below the stat strip and health grid, three Chart.js visuals turn the same metrics into an at-a-glance shape: an App Health doughnut (healthy vs errored), a Kronos Jobs doughnut (active / disabled / errored), and an SRM Status bar comparing open requests against requests added today. Each chart carries a small badge with its headline count and redraws on every 60-second refresh.
Nexus owns no tables. Platform metrics come from the Sigma API first and fall back to reading the underlying tables directly; the activity feed also pulls in SHL milestones and Chronicle articles. Every query is wrapped in a per-table try/except so a single unavailable service never breaks the whole dashboard.
kronos_jobs; also feeds the activity feed.ght_repositories. Last successful collection from ght_collection_runs.srm_requests. Excludes resolved/closed.nlg_newsletters. Unused pool from nlg_content_pool.tkn_turns across all AI sessions platform-wide.shl_entries (only rows flagged is_milestone) surface in the activity feed.herald_alerts WHERE source_app='chronicle') surface in the activity feed.Nexus owns zero tables. It assembles the full ops picture on demand from seven live blueprint data sources — no duplication, no staleness.
Apps, Kronos jobs, GHT repos, SRM requests, NLG content pool, and TKN spend — aggregated from seven live tables into a single-screen status snapshot updated on every load.
The last 20 platform events from Kronos, GHT, SRM, SHL milestones, and Chronicle articles unified in one chronological stream. Color-coded badges surface failures instantly without drilling into individual apps.
An App Health doughnut, a Kronos Jobs doughnut (active/disabled/errored), and an SRM Status bar chart turn the same headline metrics into a shape you can read in a glance.
Platform status and the activity feed are exposed as MCP tools (nexus_platform_status, nexus_activity_feed) so an assistant can query live ops data via an X-MCP-Key header, no browser session required.
A pass/fail tile for every registered app, built dynamically from the blueprint registry and refreshed by polling each /health endpoint. Newly added apps appear automatically; results are cached 60 seconds.
Download the entire platform status snapshot as a CSV — one row per metric — for spreadsheets, reporting, or feeding into other tooling.
Total AI token consumption and cumulative USD cost from TKN across all sessions platform-wide — visible at a glance on the status panel alongside Kronos and SRM metrics.
Every data source query is individually wrapped in try/except. A single unavailable table returns a zero and the rest of the dashboard continues unaffected — no cascading failures.
All 22 platform apps. Live health. Activity feed. Scheduled job dots. One screen. No SSH required.
Launch NexusRequires a MelTuc account. Create one free.