5. Where the reference boards don't scale, and our adaptation

5.1 Dense operational tables (Inventory, Ledger, Stocktake, Transfers, Audit, Reports, Payments)

The reference boards’ biggest list has 4 rows and 3 columns. SpaceWorks lists run to hundreds of rows and 8+ numeric columns, sorted, selected in bulk and exported. Card rows (82 px) would cut density by about 60%.

• Adaptation: keep DataTable, but inside the R4 card chrome (bordered, radius 12; header row 40 tall with 13 muted sentence-case labels; body rows 52–56 tall; hairlines; tabular numerals right-aligned). Sticky header. A column picker. A selection checkbox column, and the bulk bar (sticky) instead of toolbar buttons. Row click opens the detail; the row menu holds the rest.
• Filters as tabs (P8) for the 3–5 most common states. Everything else goes in a “Filters” popover with removable chips.
• Under md, rows become stacked cards (PLAN §3.5 DataTable addition).
• Stat cards above a table only when they are also filters (clicking “Low stock 12” applies the tab).

5.2 Evidence capture (issue/return photo, remark, box and asset QR)

The reference boards capture nothing heavier than a QR scan. SpaceWorks evidence is mandatory, immutable, uploaded through a presign to staging, and auditable.

• Evidence tile (new primitive): a 16:9 dashed placeholder labelled “Issue photo · Required” with “Take photo” (primary, uses the existing CameraCapture) and “Upload from device” (link). The states are uploading (progress bar plus cancel), attached (thumbnail, “Photo #182 · attached 10:42”, “Retake”), and error (“Upload failed. Your photo is still on this device. Try again.”).
• It is never displayed via a public URL. Previews use the signed-URL fetch already in QueuesList.
• No Undo after confirm: the summary before confirming replaces it (S3 step 4). Copy must not promise deletion of an uploaded photo unless the deployment’s abandoned-upload cleanup is on.
• Required-ness is visible before the user reaches the button: a “Required” chip on the step, and a step rail showing a red dot for missing required evidence.

5.3 Multi-step guided flows

The reference boards have none (their forms are single page). SpaceWorks has 5-step handovers in modals. Adaptation: a task-mode shell (sidebar hidden, step rail plus a camera/work panel, the same on kiosk), visually derived from R28. A “Compact view” for experts. Each completed step echoes its captured value in the rail.

5.4 Permission and module density

The reference boards have 4 nav items and owner/admin roles. SpaceWorks has 42 gated tabs, custom roles with dozens of actions, and module switches. Adaptation: §2 sections with “More” disclosure and flattening rules. The role editor uses R6 checkbox cards grouped by area rather than a flat checkbox list. Gated items are absent, never disabled, except reports, where an unavailable report explains which module enables it.

5.5 Settings scale

The reference settings page has 3 rows. SpaceWorks has about 30 sections. Adaptation: an in-page sub-nav with scroll-spy (S9), a per-section dirty-state Save, and one danger zone at the very end.

5.6 Dashboard breadth

The reference boards show 4 stats. SpaceWorks has 17 possible tiles. Adaptation: priority-ranked top 4 plus an “Everything else” disclosure. Tone on the number, not the fill.

5.7 Multi-tenant switching

The reference boards show one org in the switcher. Superadmins may see dozens of makerspaces. Adaptation: the switcher menu has search, recents first, and a “Switch makerspace” full list for superadmin. Single-tenant lock hides the chevron (the card is static).

5.8 Offline and kiosk integrity

The reference offline story is a callout with “Download guest list”. SpaceWorks kiosks keep an encrypted command queue with replay recovery. Adaptation: a persistent connection pill in the station header, P5 panel callouts for offline state, a queue table with per-command status, and a destructive-confirm dialog for “lock with pending work” (safe action as primary).

5.9 Money

The reference boards cover free events only. Payments need receipts and append-only corrections. Adaptation: no Undo and no inline edit. “Record payment…” opens SettlementDialog (method, reference, date). Corrections appear as “Amended” rows linked to the original. Amounts are always shown with currency, right-aligned with tabular numerals.

5.10 Activity rail data

The reference rail is free. SpaceWorks audit is permission-gated and can be large. Adaptation: the rail renders only when canViewAudit (or uses the actor’s own notifications), is capped at 6 items, and links to S15 with filters. It is hidden on narrow screens and for scoped roles whose audit would be empty.

Part of Space Works UX spec, published from docs/ux-spec.md. Edit it there.