Launch Control / Live Platform State

Tactical launcher, now tied to live platform records.

The launcher keeps the defense-ops aesthetic, but every number now comes from the backend. When the API is quiet or incomplete, the UI says unavailable and leaves the state explicit.

Enter Command SurfaceOpen Mission Site
Cloud topology
Vercel frontend / Fly API / private ML lane
Managed services stay behind the product shell instead of local-only state.
Operational doctrine
Live data or explicit empty state
The launcher reports only current backend counts and explicit empty states.
Current API route
https://adversaryai-api.fly.dev
This is the backend the launcher is reading right now.
Live posture board
Current platform state
Operational
Properties loaded
0
Live records returned by the properties API in this request.
Active certifications
0
Live certification records returned by the certification API.
Open assignments
0
Marketplace listings currently open for staffing.
Active mesh dispatches
0
Real dispatch objects currently registered in mesh state.
Control plane
Operational
Health endpoint responded successfully
Tracked assets
0
Live property count from analytics
Open incidents
0
Unresolved incidents from analytics
On-duty operators
0
Operators marked on duty in the backend
Active certifications
0
Active certification records
API uplink
adversaryai-api.fly.dev
Current backend route
Product Surfaces

Every route card now reflects live platform state.

The mission cards below retain the tactical visual language, and their telemetry rows are tied directly to current backend counts.

Sector Readiness Matrix

Grouped from live property and incident data

These sector rows are calculated from the properties and incidents returned by the backend in this request.

No live properties loaded
The launcher did not receive any property records from the API, so sector readiness cannot be computed yet.
Engagement Doctrine

Design intent without telemetry inflation

These phases describe how the real platform is supposed to operate. They are workflow doctrine, not a telemetry feed.

Phase 01
Detect
Receive live properties, incidents, operator state, and certification records from the backend.
Phase 02
Qualify
Use real certification records and current on-duty status to understand who can respond.
Phase 03
Deploy
Route operators through the command, certification, or campus surface based on actual platform conditions.
Phase 04
Review
Show empty states whenever the backend lacks data instead of manufacturing numbers for polish.