Governed Browser Shell

Operations Web now has a real frontend boundary.

This shell intentionally stops before live data wiring. The goal of this packet is boundary creation, not accidental client admission.

Target app
apps/operations-web
Public API base
https://control.apexpowerops.com
Supabase browser values
Configured locally

Package boundary

landed

A real Next.js app package now exists under apps/operations-web.

Browser env contract

configured

Public browser config values are present.

Data boundary

backend-routed

The first live read now flows through a governed control-plane route rather than direct browser database admission.

Relay browser slice

backend-routed

Relay browse and preview now stay inside the browser shell by consuming the mounted read-only relay API.

Breaker browser slice

backend-routed

ETU, TMT, and EMT breaker resource browsing now consumes governed context, settings, and static plot routes.

Operations visibility seam

backend-routed

The first Operations Visibility rollup now flows through /api/v1/ops/master-operations instead of direct browser database admission.

Schedule health seam

backend-routed

The second governed Operations Visibility seam now reads /api/v1/ops/schedule-health for scope-level risk visibility.

Scope KPI seam

backend-routed

The third governed Operations Visibility seam now reads /api/v1/ops/project-apparatus-summary for scope-level KPI rollups.

Category seam

backend-routed

The fourth governed Operations Visibility seam now reads /api/v1/ops/apparatus-by-category for grouped apparatus rollups.

Blockers seam

backend-routed

The fifth governed Operations Visibility seam now reads /api/v1/ops/blockers-summary for blocker aggregation.

What This Shell Does

  • Creates a governed frontend package and source tree.
  • Establishes the first browser-side environment contract.
  • Consumes the first live study-resource read through the governed control-plane API.
  • Consumes the first Operations Visibility dashboard rollup through the governed ops API.
  • Consumes the adjacent Operations Visibility schedule-health rollup through the same governed ops API boundary.
  • Consumes the adjacent Operations Visibility scope KPI rollup through the same governed ops API boundary.
  • Consumes the adjacent Operations Visibility category rollup through the same governed ops API boundary.
  • Consumes the adjacent Operations Visibility blocker aggregation through the same governed ops API boundary.
  • Consumes the bounded relay discovery, context, settings, and preview seam through the same governed API boundary.
  • Consumes bounded ETU, TMT, and EMT breaker resource discovery, settings, and static plot seams through the same governed API boundary.
  • Hosts the preserved cross-surface validation dashboard at /integration-dashboard/index.html.
  • Hosts the re-homed lead operations prototype at /lead-ops/index.html.
  • Hosts the promoted lead assignment app route at /lead-ops.
  • Hosts the promoted field technician app route at /field-tech.
  • Hosts the promoted PM drivers app route at /pm-review.
  • Hosts the visual PM project overview route at /pm-review/project-overview.
  • Hosts the read-only PM workfront app route at /pm-review/workfront.
  • Hosts the read-only Project Miner intake workbench at /pm-review/import-intake.
  • Hosts the read-only PM import-candidate review route at /pm-review/import-candidate.
  • Hosts the read-only PM import-admission plan route at /pm-review/import-admission-plan.
  • Hosts the read-only PM import-approval readiness route at /pm-review/import-approval-readiness.
  • Hosts the promoted PM approval app route at /pm-review/approval.
  • Hosts the promoted PM schedule app route at /pm-review/schedule.
  • Hosts the promoted PM tracer app route at /pm-review/tracer.
  • Hosts the promoted PM variance app route at /pm-review/variance.
  • Hosts the first re-homed PM read-only review slice at /pm-review/index.html.
  • Hosts the re-homed PM approval prototype shell at /pm-review/approval-surface.html.
  • Hosts the re-homed PM schedule slice at /pm-review/schedule.html.
  • Hosts the re-homed PM upstream tracer slice at /pm-review/tracer.html.
  • Hosts the re-homed PM variance slice at /pm-review/variance.html.

Next Safe Moves

  1. Now that promoted PM routes preserve return-path context and tracer can infer seeds from governed origins, stand up the bounded seam services and validate that those handoffs carry real schedule and approval data instead of shell-derived fallbacks.
  2. Use bounded backend seams for additional live reads instead of widening direct browser database authority.
  3. Treat /api/v1/ops/master-operations as the first governed dashboard rollup seam for the newly live 09 schema tranche.
  4. Treat /api/v1/ops/schedule-health as the adjacent scope-level risk seam for the same governed operations lane.
  5. Treat /api/v1/ops/project-apparatus-summary as the adjacent scope KPI seam before widening into grouped category or blocker views.
  6. Treat /api/v1/ops/apparatus-by-category as the grouped category seam before widening into blocker-note aggregation.
  7. Treat /api/v1/ops/blockers-summary as the final populated blocker aggregation seam before considering empty live views.
  8. Exercise the new apparatus study-resource route against a migrated host surface when runtime proof is needed.
  9. Keep relay preview source-faithful by surfacing storage-kind identity and unsupported warnings rather than simplifying them away.
  10. Keep the legacy Supabase browser client deferred until a separate client-shape admission decision lands.

Validation Surface

The browser-side cross-surface dashboard has been re-homed into the active operator shell and remains available at /integration-dashboard/index.html.

The lead operations prototype is available in the active lane at /lead-ops/index.html.

The promoted lead assignment route is available in the governed shell at /lead-ops.

The promoted field technician route is available in the governed shell at /field-tech.

The promoted PM drivers route is available in the governed shell at /pm-review.

The visual PM project overview route is available in the governed shell at /pm-review/project-overview.

The read-only PM workfront route is available in the governed shell at /pm-review/workfront.

The read-only Project Miner intake workbench is available in the governed shell at /pm-review/import-intake.

The read-only PM import-candidate review route is available in the governed shell at /pm-review/import-candidate.

The read-only PM import-admission plan route is available in the governed shell at /pm-review/import-admission-plan.

The read-only PM import-approval readiness route is available in the governed shell at /pm-review/import-approval-readiness.

The promoted PM approval route is available in the governed shell at /pm-review/approval.

The promoted PM schedule route is available in the governed shell at /pm-review/schedule.

The promoted PM tracer route is available in the governed shell at /pm-review/tracer.

The promoted PM variance route is available in the governed shell at /pm-review/variance.

The first PM drivers review slice is also available in the active lane at /pm-review/index.html.

The PM approval prototype shell is available at /pm-review/approval-surface.html.

The PM schedule slice is available at /pm-review/schedule.html.

The PM upstream tracer slice is available at /pm-review/tracer.html.

The PM variance slice is available at /pm-review/variance.html.

First Operations Visibility Consumer Seam

Read the master operations dashboard through the governed ops API.

This panel consumes `v_master_operations` through a read-only backend route instead of widening the browser boundary to direct Supabase reads.

Loading the governed operations rollup…

Adjacent Operations Visibility Consumer

Read scope-level schedule health through the governed ops API.

This panel consumes `v_schedule_health` through a read-only backend route so scope risk visibility stays inside the governed browser boundary.

Loading the governed schedule health rollup…

Adjacent Operations Visibility Consumer

Read scope KPI rollups through the governed ops API.

This panel consumes `v_project_apparatus_summary` through a read-only backend route so scope-level KPI visibility stays inside the governed browser boundary.

Loading the governed scope KPI rollup…

Adjacent Operations Visibility Consumer

Read grouped apparatus categories through the governed ops API.

This panel consumes `v_apparatus_by_category` through a read-only backend route so grouped apparatus breakdowns stay inside the governed browser boundary.

Loading the governed category rollup…

Adjacent Operations Visibility Consumer

Read blocker aggregation through the governed ops API.

This panel consumes `v_blockers_summary` through a read-only backend route so blocker visibility stays inside the governed browser boundary.

Loading the governed blocker summary…

First Governed Consumer Seam

Read apparatus study resources through the control-plane API.

This explorer uses the bounded backend route rather than reopening direct browser database access.

Enter an apparatus UUID to exercise the new governed backend route from the browser shell.

Breaker Resource Browser

Browse breaker resources through ETU, TMT, and EMT routes.

This browser slice is read-only and renders only server-returned context, settings, and static curve points.

CatalogUnknown
Manufacturersn/a
ETU sensorsn/a
Active familyETU
Axis 1Breakerunavailable
Axis 2Trip unitunavailable

Browse a trip unit type, select one returned row, then load the governed context, settings, and static trip curve.

Tranche 5 Browser Consumer

Browse relay TD-sections through the governed control-plane routes.

This browser slice stays read-only, preserves relay family identity, and surfaces unsupported behavior instead of hiding it.

Search the governed relay catalog to choose one TD-section, then optionally add one compare section before loading any read-only relay context, settings, or preview data.