6. Items that need a decision or data before implementation

Current rule (v2.0.1, 2026-11-13): This heading is a historical implementation checklist, not an assertion that all entries are still undecided. Item 9’s primary fill is settled: product accent is Maker Teal and tenant brand is public/member only. Other endpoint/data availability must be verified in the app; do not infer it from the age of this list. (1A-N25) — supersedes the line above; see docs/current-rules.md#cr-scope-01.

1. Request tab counts and the sidebar Requests badge. Use per-query count (free in the default view) and the cached dashboard query for the sidebar. Confirm the dashboard endpoint is readable by every actor who sees Requests; otherwise show no badge for them.
2. Event check-in Undo only if a reversal endpoint exists. Do not render Undo otherwise.
3. Invite preview (makerspace name and role on S22) needs a token-preview endpoint; fall back to generic copy.
4. Cross-space bookings list for the S13 Requests and Upcoming tabs. Without it, use the minimum variant.
5. Event aggregate stats (Going, Awaiting approval) need server counts; never sum a page.
6. Public item “Add to request” (S18) is a small behaviour change (shared cart across routes). It needs owner approval.
7. Settings deep links: in-page anchors (no routing change, recommended) vs settings/<section> subpaths.
8. Test pins that change: Dashboard h1 (keep), the “Inventory” nav label becoming “Items” (the panel heading pin is kept), member role=tab (PLAN Phase 4), and the dock test moving to the sidebar test.
9. Primary colour (PLAN open question 3) affects only fills. Every pattern above is colour-agnostic.

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