01Hierarchy

Surface tree

Three slots in the main menu, plus Settings. Two shared Detail Panels mount as slide-overs from the main pages, with deep-link routes for power users. Role routing is provisional silo (validate with Elad before locking, AB-030).

Main menu / Workshop + Weekly are the two surfaces being designed
PG operational hub · designed now
Workshop
PG day-to-day work surface. Single unified playable-as-task list with a Pipeline Tracker top section, an Ideas side panel, a Feedback side panel, and a Pace observability strip. Detail Panel mounts from any row. Absorbs V1 Delivery, Ideation PG fragments, and Pipeline Tracker (V1 /tracking). Named "Workshop" 2026-05-09, PG-as-craftsperson framing.
New M2 PG primary TL cross-view /workshop
cross-system join · V1 /tracking absorbed
Monday
Auditor
Apollo
Build
Delivery
Needs action Aging watch Send to client Per-game pace Revisions priority
Deep Ocean TreasuresBestPlay · Tatiana · revision · day 3
Disney Solitaire 0411SuperPlay · Lex · ready to send
Royal Match S07CrazyLabs · Daria · build failed
Wordscapes ArenaTripledot · Veronika · waiting on idea
Match-3 BanditCrazyLabs · Tatiana · TL approval
Royal Match42 / 60
Disney Solitaire70 / 60
Deep Ocean28 / 60
Detail Panel mounts from any row (slide-over) Open decisions: tracker default state · view shape · ideas placement · feedback affordance
Weekly
M1 launching
Mon-Fri kanban grid. Auditor rows, task cards, quota backlog right rail, manage-quotas modal. Absorbs Revisions backlog, per-auditor Monday view, build chips, carryover group. Partner surface to Workshop, both consume the same orchestration-layer state.
  • M2 add Auditor Detail drawer (Tatiana P63), per-auditor Monday-morning view absorbed from V1 Auditors
  • M2 add Carryover group in Quota Backlog (P70), unfinished items roll forward by default
  • M2 add Build chip on ply-cards, opens Build Detail drawer (status, retry, Apollo deep-link)
TL primary PG read-mostly /weekly
Settings
5 sub-sections
Full-screen surface. Barely opened daily, can hold a lot. Admins write, Head-of-PG writes entities + allocations, TLs write own team allocations, PGs write owned games. Out of design focus for Sunday review.
  • Games per-game tile + side-panel edit (quota, Slack, drives, lifecycle). CSV bulk-import flow lives here.
  • Allocations three matrix sub-views (PG↔Auditor, TL↔Auditor, PG↔TL) with show-orphans toggle
  • Capacity default working hours, effort per task type, plus vacation / sick / recurring auditor availability as overrides
  • Builds three tabs (Active, Stuck-Failed default, Completed) over V1 Builds chrome
  • Admin hard-gated (cosmo-admin Cognito group). Orphan Tasks repair, Delivery Report reconcile, admin-side imports.
Admin write Everyone reads /settings
Schedulesfolded into Capacity (vacation, sick, recurring availability are capacity overrides)
Importsa flow inside Settings:Games (CSV bulk import) or Settings:Admin, not its own sub-section
User prefslives in the profile menu (top-right avatar dropdown), not Settings nav
Monitoringsplit TBD per AB-081, decide post-Sunday
Detail panels / shared, two mount modes

Playable Detail Panel

slide-over · /task/:taskId
Mounts from Workshop (main list + Pipeline Tracker top section) and Weekly. Header + State history + Apollo/Build/Idea panels + Feedback thread + Revision status. Six IDs hidden by default in Technical details.
All roles Active V2 AB-083, AB-090, AB-078, AB-079

Game Details Panel

slide-over · /game/<id> · secondary
Mount via View Game from anywhere; standalone deep-link /game/<id>. Same content component, two modes. Routing decision post-Sunday (AB-097).
All roles Active V2 AB-095, AB-096, AB-097, AB-098
Deep-link routes / power users + admin
12 V1 surfaces dropped or folded expand for table
V1 surface Reason dropped Disposition
Status Observability only. Currently broken (P1, P34). Two-bar pace pattern → PG Op observability strip. Full charts → M3.
Dashboard Observability only. Near-empty body, no clear primary user. Aging-table fragment → PG Op Aging view. Trend chart → M3.
Ideation No coherent purpose in V2. Fragments redistribute. Send-to-Apollo automated. Ideas side panel in PG Op. Import tab → Settings:Imports. Revisions → Weekly Detail Panel.
Auditors Broken metrics (P14, P30: 1,447 Failed vs 2 Done). Observability only. Monday-morning view → Weekly Auditor Detail drawer (P63). Stats → M3. Allocation → Settings.
Builds (page) Operational monitoring, not a nav destination. Settings:Builds three-tab view (Active / Stuck-Failed / Completed).
Delivery (page) Spine list becomes Workshop main view. Workshop primary view. delivery.html prototype is the starting shape.
Feedback (page) No clear primary user. 3,988 entries, zero aggregation. Per-playable thread → Detail Panel. Flat-list log: Settings:Monitoring or drop (AB-080).
Revisions (page) Operational + observability split. Operational → PG Op (status filter) + Detail Panel history. Observability → M3.
Scorecard (page) Observability only. Best-designed surface today; M3 design pattern source. Pipeline breakdown chips + gap-to-pace → Game Details panel header. Trends → M3.
Execution Monitoring Read-only incomplete table. Two of six columns hardcoded zero. Drop entirely. "Stuck orchestration" alert can surface in Settings:Admin or Workshop tracker section.
Conversational Insights Concept stub. Hardcoded mock Q+A, no backend, never shipped. Drop entirely. Verify with Sergey/Lee no stakeholder expectation.
Admin nav slot Admin-gated menu entry. Tools fold into Settings. Settings:Admin (hard-gated to cosmo-admin Cognito group).
Deferred to M3 / observability layer
27 observability jobs deferred to M3
M2 ships the operational restructure that makes the M3 observability split possible and coherent. Prerequisite: single canonical state machine + agreed metric definitions (AB-089). V1 has at least three incompatible status taxonomies and revision-count mismatch across four pages.
SEE SECTION 03 ↓
02Flow

Surface relationships

Workshop and Weekly are the two surfaces being designed. Both consume from a shared orchestration layer (Apollo events, build events, ideation events, state machine). Detail Panel mounts as a slide-over from either. Settings sits to the side as a small full-screen surface. Game Details panel is secondary. Dropped V1 fragments fold in lightly.

ORCHESTRATION LAYER Apollo events · Build events · Ideation events · State machine both surfaces consume from this shared spine Weekly M1 LIVE TL primary /weekly TL kanban view. Mon-Fri grid, auditor rows, quota backlog rail. M2 ADDITIONS Auditor Detail drawer (P63) Carryover group in Quota Backlog (P70) Build chips on ply-cards + Build Detail drawer Detail Panel mounts from any task card (slide-over) Workshop NEW M2 PG primary /workshop PG operational hub. Pipeline Tracker top section + 5 named views + panels. TOP SECTION Pipeline Tracker (V1 /tracking absorbed) 5 NAMED VIEWS Needs action · Aging · Send · Per-game pace · Revisions Pace observability strip (in-context M2) SIDE PANELS Ideas panel (Request Ideas, Add Prompt) Feedback panel (Internal + Client thread) OPEN AB-070 view shape, tracker default state Detail Panel mounts from any row (main list or tracker section) Playable Detail Panel shared component, slide-over from any host page Header · State History · Apollo · Build · Idea · Feedback · Actions Six IDs hidden in Technical details (collapsed by default) slide-over · /task/:taskId deep-link AB-083, AB-090, AB-078 Settings /settings · config + admin Games · Allocations · Capacity Builds · Admin 5 sub-sections Game Details /game/:id · secondary 4 KPI · Pipeline strip ACK · Activity · Tile gallery routing TBD: AB-097 View Game DEEP-LINK ROUTES /task/:taskId /orchestration/:id /game/:id DROPPED V1 SURFACES (folded) Status · Dashboard · Ideation · Auditors · Builds-as-page · Delivery-as-page Feedback-as-page · Revisions-as-page · Scorecard-as-page · Execution Monitoring Conversational Insights · Admin nav slot fragments folded to Workshop, Settings, and Detail Panel OPEN DECISIONS · POST-SUNDAY AB-070 Workshop view shape (list-as-spine) AB-097 Game Details routing (slide-over + deep-link) AB-081 Settings split (config vs monitoring) Pipeline Tracker default state (collapsed vs expanded) consume from / mount to deep-link / cross-page jump View Game (secondary)
03Observability layer / M3

27 jobs deferred

M2 ships the operational restructure that makes the M3 observability split possible. Per-role wishlist below grounded in the vault. Implementation order decided when M3 planning begins, post-M2 ship.

PG
8 jobs
  • Quota pace per game (two-bar pattern from Status, M3-trustable)
  • Aging items: Ready-to-send sitting too long (P31, Einat 2-day threshold)
  • Revision rate per game and trend (Harel primary ask)
  • Fix-type breakdown of revisions (technical / quality / design / copy)
  • Per-game pipeline breakdown chips (Ideas → Apollo → ... → Accepted)
  • Prompt-to-Apollo tracking (which sent, failed, waiting)
TL
6 jobs
  • Per-auditor open-tasks + revisions on Monday morning at scale (P63)
  • Build failure notifications routed to owning auditor + TL (P6, P13)
  • Revision throughput trend: open vs resolved, repeat patterns
  • TL approval bottleneck surfacing (60/day vs 6/day target, P48)
  • Demand-chain health: prompt coverage for next week (P47)
  • Auditor availability: vacation, sick, free days (P33)
Auditor
3 jobs
  • Build failure notification, see what went wrong without TL relay
  • See client feedback on own work after TL routes it
  • Task queue visibility: priority order, what's expected today (P46)
Admin / Leadership
6 jobs
  • Portfolio delivery health: quota, delivered, pace, gap-to-close (P21)
  • Game health drill-down: Behind / At Risk / On Track / Not Started
  • Revision rate trend: is quality improving?
  • TL approval bottleneck as portfolio constraint (P48)
  • McSett autonomous agent monitoring (success / escalation / active)
  • Partner-level delivery roll-up (revision rate by partner)
Customer
1 job
  • Receive structured delivery report: sent / approved / in revision (JTBD-15)
  • Yuval data question: contractual quota vs executed vs sent vs revised, per game / PG / total
Green-field
3 jobs
  • Translation chain quality from prompt to execution per game (Harel R2 thesis)
  • Quiet client churn detection before partner disengages (Fishi)
  • Expected delivery simulation given week plan + capacity (Einat)
Prerequisite before any M3 surface ships
Single canonical state machine + agreed metric definitions (AB-089). V1 has at least three incompatible status taxonomies and revision-count mismatch across four pages (34 / 104 / 181 / 244, P29). Observability numbers cannot be trusted until the data layer is reconciled.
AB-089 must