UX Mockup Backlog Triage — 2026-06-10

Scope: All directories and flat files under docs/ux/ as of 2026-06-10. Produced by: software-architect — triage only. No files moved, no issues closed.

Directory inventory

Total entries under docs/ux/: 9 (6 directories + 3 flat .md files).

Classification breakdown: 0 LIVE / 2 IN-FLIGHT / 0 STALE / 5 SUPERSEDED / 1 NEEDS-DECISION

Per-entry rationale

1. beta-admin/ — IN-FLIGHT

Epic #3403 (epic(beta): Phase-1 closed-beta tester program) is open with needs-grooming. Multiple implementation PRs have already merged against this design (#3417, #3420, #3421, #3422, #3428, #3436, #3437, #3446, #3466). The wireframes cover the full admin surface (tester list, add-tester form, weekly digest, settings). Several open questions from the wireframe README (admin hosting, CF Access policy, sentiment score algorithm, round-2 trigger logic) remain unanswered — see NEEDS-DECISION section below. The directory is an active reference for in-progress work; do not archive.

2. beta-tester/ — IN-FLIGHT

Same parent epic #3403. The tester-facing walkthrough (welcome screen, walk steps, final survey, thank-you) is the live product for beta testers. PRs #3419, #3421, #3466 shipped the NDA gate, survey form, and cross-service token verifier against this design. Open questions on the survey rubric and URL structure remain unresolved; see NEEDS-DECISION section. Do not archive.

3. cookie-consent-banner/ — IN-FLIGHT

Card #3215 (feat(antlers): cookie consent banner on raxx.app) is open, groomed, pre-launch-blocker. Design PR #3223 (initial mockups) merged 2026-06-04. Three further open PRs exist: #3414 (3 A/B/C variants), #3415 (polish-lens pass), #3452 (Variant A copy revision removing 3P tool names after operator review). The implementation card has not been claimed; the design iteration is still live. Do not archive. Note: the operator has a CHANGES_REQUESTED review on #3414 which is blocking the copy-revision PR #3452; the design iteration is the current blocker, not the card itself.

4. market-time-widget-variants/ — NEEDS-DECISION

PR #3183 (4-variant mockups) and PR #3339 (screenshots + comparison grid) merged 2026-06-06. PR #3340 (feat(antlers): MarketTimeWidget — date line, holiday pill, pre-market/after-hours labels) also merged 2026-06-06, shipping incremental improvements to the live baseline (Variant A).

The designer's recommendation is C (Clock Face) in AppHeader compact + D (Rich Schedule) as Dashboard card (README, line 67). No operator pick has been recorded. The variants are on the current branch (design/market-time-widget-variants) as a live PR open against main.

The directory is not archivable until the operator makes a call. Feature-developer cannot claim work on B, C, or D without that decision.

Highest-priority NEEDS-DECISION item — see section below.

5. options-chain-redesign/ — SUPERSEDED

This was the ux-designer's initial redesign pass (operator brief: "clean it up, add row-action menu"). Design PR #3077 merged. Operator then reviewed 3 variants from options-chain-variants/, chose Variant A + filter chips from C. Implementation shipped via PR #3105 (feat(antlers): Options Chain V2 — Variant A mirrored layout + filter chips) and PR #3153 (mobile polish). Issues #3177 and #3150 are closed. The options-chain-redesign/ directory was the intermediate step; it has been superseded by the final variant decision and the shipped code. Recommend archive to docs/ux/archive/options-chain-redesign/.

6. options-chain-variants/ — SUPERSEDED

Same decision path as above. The operator chose Variant A + filter chips; Variants B and C were explicitly discarded per issue #3084 body. The variants directory was the decision surface; the decision was made and shipped. Recommend archive to docs/ux/archive/options-chain-variants/.

7. beta-campaign-wireframes-2026-06-08.md (flat file) — SUPERSEDED

This flat file is the wire-brief that preceded the beta-admin/ and beta-tester/ directories. Both directories contain more detailed HTML mockups and a screen index. The flat file duplicates context that now lives in the directories and in the design PR (#3408). Recommend archive to docs/ux/archive/beta-campaign-wireframes-2026-06-08.md.

8. options-chain-redesign.md (flat file) — SUPERSEDED

Top-level brief that predates the options-chain-redesign/ directory. Content was absorbed into the directory's mockups and the variant comparison. Feature shipped. Recommend archive.

9. options-chain-variants.md (flat file) — SUPERSEDED

Top-level brief for the 3-variant design. Decision made (issue #3084), feature shipped (#3105). Recommend archive.

NEEDS-DECISION: MarketTimeWidget variants

Question for operator: Which variant(s) to implement?

Designer's recommendation: Variant C (Clock Face) in the AppHeader compact slot + Variant D (Rich Schedule) as the Dashboard card widget.

The four options and their cost:

Variants are independent; any combination can ship. Operator can choose B + D, C + D, just C, just D, or keep A only.

Open question on Variant D: next_holiday field is optional; the widget hides the holiday band when absent. Backend card needed if holiday data should be live.

The current open PR design/market-time-widget-variants holds the mockups and README but has no implementation sub-cards filed.

NEEDS-DECISION: Beta program open questions (operator-decision surface)

From the beta-admin/ and beta-tester/ wireframes, these questions remain unresolved and block full shipping:

1. Admin hosting — beta-admin.raxx.app vs sub-route of console.raxx.app. Changes which nav chrome wraps the admin UI. This affects infra provisioning.
2. Sentiment score algorithm — the 0–100 composite shown in the admin table has no defined weighting formula. PM or operator to define before the scoring pipeline can be wired.
3. Round-2 promotion logic — "Promote to next round" is manual per mockup. Auto-promotion rules (threshold + criteria) unspecified.
4. CF Access / settings page access control — who else besides the operator can see beta-admin?

These are documented in the wireframe README (lines 47–56) but no issue or operator-decision label has been applied to #3403 to track them. Card-groomer should surface these on #3403 before the next sprint.

Cookie consent: in-flight design chain

For orientation, the full chain of cookie consent design work:

Implementation card: #3215 (pre-launch-blocker, groomed, unclaimed). None of the open design PRs need to block implementation of the chosen variant once the operator resolves the CHANGES_REQUESTED review on #3414.

Archive recommendations (no action in this pass)

Move to docs/ux/archive/ in a single housekeeping PR when the beta program and cookie consent design chains settle:

docs/ux/archive/
  options-chain-redesign/          (from docs/ux/options-chain-redesign/)
  options-chain-variants/          (from docs/ux/options-chain-variants/)
  options-chain-redesign.md        (from docs/ux/options-chain-redesign.md)
  options-chain-variants.md        (from docs/ux/options-chain-variants.md)
  beta-campaign-wireframes-2026-06-08.md

Trigger: after the operator resolves the MarketTimeWidget variant pick and closes #3415/#3452 — that's the natural "design sprint settled" moment for this wave.

Next steps

1. Operator action (highest priority): Pick MarketTimeWidget variant(s) — B, C, D, or combination. Record the decision on the open design/market-time-widget-variants PR and file implementation sub-cards.
2. Operator action: Resolve CHANGES_REQUESTED on cookie consent PR #3414 so the copy-revision PR #3452 and implementation card #3215 can unblock.
3. card-groomer action: Apply blocked:operator-decision to epic #3403 and quote the four unresolved beta admin questions.
4. Housekeeping PR (future): Move 5 superseded entries to docs/ux/archive/ after design sprint settles.