Surfaces
4
Serializable admin rows
Workflow Pattern — Admin
This study defines how page density, metrics, a client table island, status display, permission state, and composition rules work together.
Promotable admin patterns need server-owned data assembly, serializable rows, narrow client callbacks, and visible permission states.
§01
The dominant metaphor is a control plane: metrics set the operating context, the client table island handles interaction, and status panels make failure states visible.
Surfaces
4
Serializable admin rows
Queue
24
Open operational items
Watch
1
Needs admin attention
Blocked
1
Requires escalation path
Control-plane dashboard
This study keeps the useful admin density while replacing tutorial code blocks and raw color maps with canonical metric, status, and table primitives.
| Surface | Owner | Status | Queue | Updated |
|---|---|---|---|---|
| Access review | Security | Watch | 7 | Today |
| Plan governance | Platform | Healthy | 3 | Yesterday |
| Evidence intake | RFP Ops | Healthy | 12 | Mon |
| Billing controls | Finance | Blocked | 2 | Last week |
Rule 1
RSC owns data assembly and page shell.
Rule 2
Metric grid appears before client table island.
Rule 3
Client table receives serializable rows and callback contracts.
Rule 4
Status bands expose operational risk without raw color maps.
Rule 5
Anti-pattern notes stay as evidence, not tutorial chrome.