Wave A service inventory

Service inventory evidence

Compare fixture-backed service records using only backend-authorized labels, source posture, timestamps, and safe summaries.

Read-only route
Fixture-backed

No live backend proof or protected actions

This route renders support-safe inventory fixtures. It does not fetch live data, reveal backend origins, collect credentials, or execute deploy, rollback, restore, restart, route, backup, or maintenance operations.

Current posture

Inventory proof boundary

  • Fixture-backed

    Evidence source

    All records are static support-safe fixtures and cannot be mistaken for live operational proof.

  • 4 of 4

    Visible records

    No search or state filters are active.

  • Read-only

    Backend authority

    The route maps backend-safe service inventory fields but performs no frontend fetch or protected operation.

  • Unavailable

    Protected actions

    Deploy, rollback, restore, restart, route, backup, and maintenance actions remain explanatory only.

Local filters

Read-only service records

All fixture-backed service records are shown.

Read-only fixture-backed service inventory. No row executes protected operations.
ServiceStateRoute postureDeploy / backup / audit postureSourceDetail posture
Derbent app APIsvc-derbent-api
Environment
operator
Lifecycle
runtime foundation
availableRead-only status, service, route, deployment, backup, audit, access, and authority routes are represented by backend-owned contracts.

Deployment history is read-only evidence; deployment and rollback execution are unavailable.

Backup evidence is read-only; backup and restore execution are unavailable.

Audit evidence is fixture-backed; audit persistence remains backend-owned.

static fixture2026-06-05T12:00:00ZDetail route planned

Support-safe inventory labels mirror backend read-model fields without exposing host, origin, or command details.

Control-plane evidencesvc-control-plane
Environment
operator
Lifecycle
Wave A read model
degradedRoute inventory summaries are available as bounded labels; route mutation and proxy operations are unavailable.

History can be inspected as fixture-backed evidence; live adapters are absent.

Restore proof and retention posture are visible as labels only.

Read-only audit summaries include safe request and correlation identifiers only.

static fixture2026-06-05T12:00:00ZDetail route planned

The route is useful for comparison, but it does not prove live infrastructure or protected action authority.

Restore evidence posturesvc-restore-evidence
Environment
operator
Lifecycle
planned operation proof
plannedNo route mutation surface exists for this record.

No deployment control is exposed from the inventory.

Restore proof remains planned until backup and restore execution contracts exist.

Audit persistence and protected action trails remain planned.

static fixture2026-06-05T12:00:00ZDetail route planned

This fixture labels future restore evidence posture without claiming a completed restore or showing storage internals.

Operation authority gatesvc-operation-authority
Environment
operator
Lifecycle
fail-closed access posture
unavailableAccess and operation-authority reads fail closed until production identity and policy integrations exist.

Deployment, rollback, restart, and maintenance operations are blocked.

Backup and restore operations are blocked.

Approval and audit persistence are unavailable for protected actions.

static fixture2026-06-05T12:00:00ZDetail route planned

Operators can inspect the denial posture, not bypass it or trigger protected work from the browser.

Required states

State coverage and safe recovery

  • Default

    The default route shows all fixture-backed service inventory rows and keeps source labels visible.

  • Loading

    Future backend reads should preserve this table shape with progress text or skeleton rows while evidence loads.

  • Empty

    A zero-record response is distinct from filters hiding records or authority being unavailable.

  • No match

    Search and state filters render a specific no-match message with a reset path.

  • Partial data

    Missing route, deployment, backup, or audit families must stay labelled rather than implying complete evidence.

  • Stale

    Checked timestamps stay visible so fixture-backed or future backend evidence cannot look fresher than it is.

  • Unavailable

    Unavailable authority is explanatory and does not become a disabled deploy, rollback, restore, route, backup, or maintenance button.

  • Auth required

    Production sign-in and session semantics remain backend and identity work, not frontend fixture proof.

  • Permission denied

    Denied states show safe request or support identifiers only and never display tokens, claims, or policy internals.

  • Safe error

    Error copy should state that no action changed and use bounded support-safe identifiers instead of stack traces.

Honest authority

Unavailable protected actions

  • DeployUnavailable authority

    Requires backend preflight, permission, approval, execution result, failure handling, and audit contracts.

  • RollbackUnavailable authority

    Requires backend preflight, permission, approval, execution result, failure handling, and audit contracts.

  • RestoreUnavailable authority

    Requires backend preflight, permission, approval, execution result, failure handling, and audit contracts.

  • RestartUnavailable authority

    Requires backend preflight, permission, approval, execution result, failure handling, and audit contracts.

  • Route changeUnavailable authority

    Requires backend preflight, permission, approval, execution result, failure handling, and audit contracts.

  • BackupUnavailable authority

    Requires backend preflight, permission, approval, execution result, failure handling, and audit contracts.

  • MaintenanceUnavailable authority

    Requires backend preflight, permission, approval, execution result, failure handling, and audit contracts.

Fixture-backed service fields map to backend-authorized service inventory labels: stable IDs, display labels, environment, lifecycle, state, source, checked timestamp, and support-safe summaries.

Route, deployment, backup, and audit posture columns are summaries only; they are not live adapters, operational proof, or backend-origin disclosure.

The search and state filter are local read-only affordances over fixture fields and never initiate protected Derbent operations.