Skip to content

feat(operator): show active deployment state#52

Open
0xMuang wants to merge 1 commit into
feature/demo-one-command-launcherfrom
feature/operator-dashboard-deployment-state
Open

feat(operator): show active deployment state#52
0xMuang wants to merge 1 commit into
feature/demo-one-command-launcherfrom
feature/operator-dashboard-deployment-state

Conversation

@0xMuang

@0xMuang 0xMuang commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

What changed\n\n- show active asset profile, network, venues and governance approval count\n- show artifact-driven RWA token, Router, RFQ adapter, AMM adapter and pool addresses\n- preserve the read-only operator boundary and raw event view\n\n## Verification\n\n- operator dashboard smoke test\n- git diff --check\n\nCloses #51

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant