From 45964c9a3751d0239a8e737d61ffb586e7c610f4 Mon Sep 17 00:00:00 2001 From: Muang Date: Wed, 22 Jul 2026 18:54:10 +0900 Subject: [PATCH] Make deployment state legible in the operator view Operators need to identify the active asset and execution wiring without opening raw artifacts or event JSON.\n\nConstraint: the dashboard remains read-only and all addresses continue to come from the Operator API deployment artifact.\nRejected: adding mutation controls to the first operational view | governance actions require external multisig review and a separate feature.\nConfidence: high\nScope-risk: narrow\nDirective: Keep display-only state separate from future proposal and execution workflows.\nTested: npm test --prefix services/operator-dashboard; git diff --check.\nNot-tested: browser visual QA and production indexer data. --- services/operator-dashboard/index.html | 4 ++-- services/operator-dashboard/test/smoke.js | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/services/operator-dashboard/index.html b/services/operator-dashboard/index.html index 42d322f..32cfe19 100644 --- a/services/operator-dashboard/index.html +++ b/services/operator-dashboard/index.html @@ -9,12 +9,12 @@
Corner Store / local console

Compliance, visible
at settlement.

Read deployment state in Operator view. In RFQ demo, click through a signed quote, current-policy check and protected Router settlement.

-
PROFILELoading…
VENUESLoading…
CONTROL PLANERead-only snapshot
CHANGE PATHExternal multisig proposal

Indexed events

Loading…

No private keys. No direct transaction endpoint.

+
PROFILELoading…
NETWORKLoading…
VENUESLoading…
GOVERNANCELoading…

Active deployment

RWA tokenLoading…
Execution RouterLoading…
RFQ adapterLoading…
AMM adapterLoading…
AMM poolLoading…
Change pathExternal multisig

Addresses come from the selected deployment artifact. This view is read-only.

Indexed events

Loading…

No private keys. No direct transaction endpoint.