jb/shd.build
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

feat(isac): grant agents baseline data contribution access

Browse Source
This commit is contained in:
JB
2026-07-25 13:28:26 -04:00
parent 406d82991b
commit d495cd585a
8 changed files with 28 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/DESIGN_SYSTEM.md
+10
View File
@@ -531,3 +531,13 @@ data-navigation items. Proposal lifecycle states use text as well as color:
pending is orange/actionable, approved is green/configured, and rejected or
failed is red/archived. Review decisions always use the standard ISAC confirmation
surface and must never apply a proposal from a table-row click alone.
Audit History may use a five-column KPI filter rail when all durable operational
domains need first-class visibility. It retains the standard compact KPI height
and collapses through the shared dashboard breakpoints; do not increase card
height or create a second row solely to accommodate the fifth domain.
Inherent permissions that cannot be removed through role or user assignment use
the compact blue information rail above the affected access controls. Always
name the baseline and enumerate its capabilities so operators do not mistake an
empty role assignment for an account with no effective access.