Repository navigation
UI-FE-030 — Build Governance Role Administration UI #600
Description
Problem context
Role membership and grant/revoke changes must remain canonical, separated, warned, and timelocked.
Technical scope
- Implement role member/pending-change views and typed grant/revoke preparation.
- Show separation-of-duty warnings and authority sources.
- Remove any legacy-role inference from UI behavior.
Architecture and security constraints
- Follow the approved Frontend Implementation Matrix and linked boards.
- Optimism/EVM only. UI context, wallet connection, API data, or fixtures never grant authority.
- Contracts are canonical for mutations; API data is freshness-labelled projection data.
- Fixtures stay out of production. Unpinned actions render unavailable.
Required tests
- Unit/component and Storybook interaction tests for all scoped states.
- Keyboard, focus, names, contrast, reduced motion, 200% zoom, and responsive visual checks.
- Lint, typecheck, tests, Storybook build, and production build.
Acceptance criteria
- No immediate direct role mutation is exposed.
- Timelocked lifecycle and pending changes are explicit.
- Stale role evidence fails closed.
Dependencies
- EPIC V2-FE-152 — Privileged Operations, Governance, and Guardian Compositions #556
- STAB-FE-005 — Replace Placeholder Release Data with Verifiable Contract Provenance #560
- UI-FE-028
- UI-FE-029
Do not assign until dependencies are satisfied.
Non-goals
- Inventing contract/API behavior or authority.
- Changing approved designs/routes.
- Applying
Stellar Wave.
Deliverables
- Role administration composition and tests.
Complexity and points
- Complexity: High
- Points: 200
Approved visual authority
Candidate only; activation remains suspended.
Candidate points
- High — 200 points
Candidate only; activation remains maintainer-controlled.
Activity
King028 commentedon Oct 15, 2026
@King028 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @King028 to this issue.
drips-wave commentedon Oct 15, 2026
Congratulations, @King028! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @King028: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
Merge pull request #689 from King028/main
drips-wave commentedon Oct 17, 2026
This issue has been completed by @King028 as part of the Stellar Wave Program's 10th Wave 🥳
😎 @King028: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.