Add ISAC user operations and access roles

2026-07-24 23:21:28 -04:00
parent 8ecdfaa319
commit 472528f429
21 changed files with 355 additions and 49 deletions
@@ -83,10 +83,21 @@ Use the spacing tokens for new components. Prefer `8px`, `12px`, and `20px` gaps
 ### Admin dashboard

 - Use `admin-page`, `admin-command`, `admin-dashboard`, `admin-sidebar`, and `admin-content`.
+- The administrative system is named ISAC. Separate navigation into explicit
+  operational domains such as User Operations and Data Management; visibility
+  must reflect server-provided capabilities.
 - Each module starts with `module-toolbar`, followed by `module-kpis`.
 - Editors use `dashboard-editor` and appear before the affected table.
 - Data collections use `dashboard-table`, `dashboard-row`, and `table-heading`.
 - Keep tables dense and horizontally scrollable rather than wrapping columns unpredictably.
+- User dossiers pair access controls and moderation in a two-column console,
+  followed by compact login and content-history streams. Restriction state must
+  be textual and use the danger color; inactivity remains a separate activity
+  classification rather than a punishment state.
+- Role names describe durable organizational responsibility. `Admin` is the
+  unrestricted administrative role; `Moderator` is reserved for community
+  content moderation and does not imply ISAC access. Operational ISAC access is
+  delegated separately through scoped roles and permissions.
 - Threshold-based set bonuses use compact `effect-band` groups. Each threshold is
  displayed as a fixed piece-count marker followed by its mapped stat and value,
  keeping progression readable in editors and table summaries.