Skip to content

v2.50.0 — RBAC: the Operate console is the operators' app + case-detail drawer

Choose a tag to compare

View all tags
@avelikiy avelikiy released this 07 Jun 18:40
v2.50.0
This tag was signed with the committer’s verified signature.
avelikiy Alex
SSH Key Fingerprint: nD9xQzAb/3YFTUEHwDpi26wMHeq89yGJsV5XW/FadYQ
Verified
Learn about vigilant mode.
413ebb6
This commit was signed with the committer’s verified signature.
avelikiy Alex
SSH Key Fingerprint: nD9xQzAb/3YFTUEHwDpi26wMHeq89yGJsV5XW/FadYQ
Verified
Learn about vigilant mode.

Does the CTO need the admin board? No — the Operate console is the operational staff's surface (the licensed humans who sign). The CTO/admin builds in the CLI and oversees; only admin may switch to Build.

  • RBAC (scripts/lib/roles.mjs, 20 roles) — an operator role (coder · BSA officer · customs broker · CPA · QPPV …) only sees and signs the cases for its own vertical(s); compliance-lead sees every queue but can't Build; admin does everything. Enforced on the API: runs are role-filtered and approve/reject/start return 403 outside a role's verticals.
  • Console — role picker scopes the queue, hides Build + 'Start a run' for operators, restricts the start picker to the role's verticals.
  • Case-detail drawer — click a run → full step trace · accountable owner · multi-gate progress · audit trail · ⬇ Export audit (JSON).

276 lib tests (verified: a BSA officer can't see or sign an rcm case).

Assets 2
Loading