AM Pilot | Ops

Health Center

Top row explains business impact now. Lower sections show live issues and system checks. Last sync Pending.

Overall status now

Checking Loading workspace and service posture.

Workspaces impacted now

— Loading

Customer orders (7d)

— Loading

Platform API

Checking Waiting for platform heartbeat

Data pipeline

Checking Waiting for internal operations feed

App telemetry

No data No client or backend events captured yet

Healthy workspaces

— Loading

Workspaces at risk

— Checking

Customer incidents (24h)

— Waiting

Backend incidents (24h)

— Checking

Business risk

Priority actions

Waiting for tenant posture data.

Risk signals will appear here.

Active issues

Live incidents

Waiting for incident events.

Customer-facing failures will appear here.

Platform systems

Infrastructure checks

Waiting for dependency probes.

Database, storage, slicer, and feed status will appear here.

Customer posture matrix

Workspace health, activity, and issue footprint

Tenant	Admin app	Customer app	Activity	Issues

Diagnostics

Engineering drill-down

Route-level SLO, hotspot concentration, and deeper reliability checks for incident response.

SLO

API reliability SLO

Checking API reliability target.

Waiting for request samples across tenant apps.

SLO

Route latency SLO

Waiting for route latency samples.

Per-route p95 latency and objective compliance will appear here.

Backend diagnostics

API pressure points

Waiting for backend diagnostics.

Top failing and slow API routes in the last 24 hours will appear here.

Tenant diagnostics

Issue concentration

Waiting for incident concentration data.

Tenants with the highest 24h incident volume will appear here.

Error Logs

Unified client + backend incident stream with tenant scope, request tracing, and source diagnostics.

Incident stream

— Loading

Client 24h

— Loading

Backend 24h

— Loading

Slow routes 24h

— Loading

Tenant incident log

Recent retained client and backend incidents with request trace diagnostics.

Time	Tenant	App	Event	Request

Customers

Customer workspace matrix with usage, orders, and revenue across all tenants.

Sort by

Customer matrix

Commercial and adoption view by tenant: accounts, orders, revenue, and latest activity.

Customer	Accounts	Orders	Revenue	Activity

Provisioning

Workspaces, domains, first-admin access, and platform fee settings.

Workspaces

Customer list

Provision and manage customer workspaces for the platform.

0 active workspaces

Create

New workspace

Create a tenant workspace and invite the first administrator in one pass.

Tenant slug * Company name

Communication email Brand logo URL

Quote domain Admin domain

Admin email * Admin full name

Platform fee (%)

My account

Password

Update your platform-owner password for the provisioning surface.

Estimator Lab

Keep this surface focused on shadow slicing, component errors, confidence bands, and release gates. It should explain whether the estimator is trustworthy enough to ship.

Shadow mode first Target fidelity: 90%

Shadow labels

Capture ML vs native slice deltas

Per upload, persist the resolved recipe, ML prediction, native result, slicer version, and estimator version.

Error segmentation

Break time and grams by component

Model time, support time, travel time, part grams, and support grams need separate quality visibility.

Release gates

Promote only when regimes improve

Validate by printer, material, layer height, support usage, and job size before any model promotion.

Before charts

Data model that has to exist

Resolved recipe snapshot shared by ML and native slicing
Per-job labels for print time and grams from both engines
Versioning for estimator, native slicer, and config bundle
Offline retraining flow instead of direct online learning

Boundary

What does not belong here

Generic runtime incidents should stay in Health Center
Tenant onboarding should stay in Provisioning
Release actions should wait until shadow validation data is real