feat(isac): add moderated contributor mode

docs/DESIGN_SYSTEM.md

@@ -532,6 +532,44 @@ 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.
 
+Eligible contributors enter ISAC data modules in read-only mode by default.
+The access banner pairs the explicit `READ-ONLY DATA ACCESS` state with a compact
+action that opens the versioned contributor guidelines. Contributor mode may
+only be enabled after affirmative checkbox acceptance. Once enabled, the banner
+changes to orange, explains that saves enter moderation, and offers a
+`RETURN TO READ-ONLY` toggle. Disabling is immediate and reversible and does not
+withdraw existing proposals. Use text for every mode state; color alone is
+insufficient. At narrow widths, stack the explanation and full-width toggle.
+Read-only mode is an inspection surface: hide add controls, row edit actions,
+mutation forms, and editors opened through URL state. Do not merely dim or
+disable them. Registry navigation, KPI filters, pagination, search, evidence,
+and other non-mutating inspection controls remain visible and interactive.
+
+The ISAC command-status cluster includes an explicit `DATA MODE` cell alongside
+system, access, and environment. It reports the highest effective data authority
+in this order: `ADMIN`, `DATA MANAGER`, `APPROVER`, `CONTRIBUTOR`, then
+`READ-ONLY`. Use a neutral treatment for read-only, orange for contributor,
+blue for approval authority, and green for direct-management authority. The
+label and value are mandatory because color is supplemental. At medium widths
+the four cells become a two-column grid; on narrow screens the cluster spans
+the command header width.
+
+Data-navigation links with pending proposals use a dedicated four-column layout:
+module code, flexible label, square orange count cell, then navigation arrow.
+Never insert a count into the ordinary three-column link without changing its
+grid, because the arrow will wrap to another row. The count includes textual
+assistive labeling and strengthens its border and contrast on link hover or
+active state.
+
+Pending records may be used as dependencies in later proposals by any
+contributor. Render these choices in the ordinary assignment control with a
+restrained orange border/background and the explicit text `PENDING` plus the
+proposer's display name; never present them as live data. Approval is dependency
+ordered: a dependent proposal stays pending until every referenced proposal is
+approved, while rejected or failed dependencies block it. This state must be
+conveyed by text as well as color and must remain legible in compact and
+responsive editor layouts.
+
 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