Epic 14 Event Detail Redesign

Implementation seam — the 8-tab shell mounts existing components (Phase A), later phases upgrade internals. Phase A establishes the 8 tab slots and re-groups today’s components into them (consolidation containers for Communications + Wrap-up; Cockpit interim = today’s Overview content; Details surfaces today’s identity edit). This makes the shell independently shippable and beta-previewable. Phases B–F then replace each tab’s internals with the redesigned experience. Publishing and Settings are essentially unchanged by the redesign — they are satisfied by the Phase A mount of the existing EventPublishingTab / EventSettingsTab; Phase F only finalizes their placement + the small removals/guards (FR35, FR43).

# Phase A — Lifecycle foundation & shell

# Story 14.A.1: Author the workflow-state → relevance map

As a returning organizer, I want the page to know which parts of the workflow are relevant to my event’s current state, So that what I see is driven by where the event actually is — not a flat list of everything.

Acceptance Criteria:

Given web-frontend/src/utils/workflow/workflowState.ts (8 states + getWorkflowProgress/ getWorkflowStepNumber/isEarlyStage/isLateStage, no relevance map today) When the map is authored Then a single declarative table maps each of the 8 states to { cockpitEmphasis, focusTabs[], dimmedTabs[], lockedTabs[] }, and a getTabRelevance(state) helper returns the per-tab relevance (active | dimmed | locked). And the table has exactly 8 rows — CREATED, TOPIC_SELECTION, SPEAKER_IDENTIFICATION, SLOT_ASSIGNMENT, AGENDA_PUBLISHED, EVENT_LIVE, EVENT_COMPLETED, ARCHIVED — no AGENDA_FINALIZED (AR1).

Given the 8-state map When the state is CREATED … AGENDA_PUBLISHED Then Wrap-up is locked; when state is EVENT_LIVE or later, Wrap-up is active (FR5). And Cockpit, Details, and Settings are active in every state.

Given any state When getTabRelevance is unit-tested Then every state→tab pairing is asserted, and the “finalized” emphasis (final newsletter / catering offer / print agenda) is attributed to AGENDA_PUBLISHED (the 8-state reconciliation), not a separate state.

And while authoring the map, the stale “9-step” JSDoc at the top of workflowState.ts (and the // step N/9 examples on getWorkflowProgress/getWorkflowStepNumber) is corrected to 8 — (already done 2026-06-13; assert it stays 8 so it can’t regress).

Enabler-story note: this is a pure foundation story — it ships a declarative map + helper with no user-visible UI of its own (it is not independently demoable; its value is realized when 14.A.2/14.A.3 consume it). Its “done” is the helper + full unit coverage, not a screenshot.

# Story 14.A.2: 8-tab IA shell recomposing existing components

As an organizer, I want the event page organized into 8 lifecycle-aware tabs in two clusters, So that I can tell work tabs from set-and-forget config at a glance and never lose the event’s identity.

Acceptance Criteria:

Given EventPage.tsx renders 10 flat tabs today (Overview, Speakers, Venue, Participants, Publishing, Newsletter, Registrant Notices, Settings, Photos, Appreciation) When the shell is rebuilt Then the tab rail shows 8 tabs in order — 🧭 Cockpit · 🎤 Speakers & Agenda · 🎟️ Registrations · ✉️ Communications · 📢 Publishing · 🎁 Wrap-up (work cluster) then 📝 Details · ⚙️ Settings (config cluster), visually grouped with the config cluster last (FR1). And the event title remains in the page header on every tab (FR2).

Given the new slots When each tab mounts Then existing components are recomposed into them with unchanged content (FR3): Cockpit = today’s EventOverviewTab content (interim, replaced in Phase B); Speakers & Agenda = existing EventSpeakersTab; Registrations = existing EventParticipantsTab; Communications = a consolidation container holding EventNewsletterTab + EventRegistrantNoticesTab + VenueCoordinationComposer (replaced in Phase E); Publishing = existing EventPublishingTab; Wrap-up = container holding EventPhotosTab + EventAppreciationTab (refined in Phase F); Details = the existing identity edit surface (EventForm) shown in-tab (refined in Phase F); Settings = existing EventSettingsTab. And the old standalone Venue, Newsletter, Registrant Notices, Photos, Appreciation, Overview tabs no longer appear as top-level tabs.

Given the relevance map (14.A.1) When a tab is dimmed or locked for the current state Then dimmed tabs render visually de-emphasized and locked tabs render dimmed + 🔒 and are non-interactive (e.g. Wrap-up before EVENT_LIVE) (FR5).

# Story 14.A.3: Count-driven tab attention badges + task data hooks

As an organizer, I want tabs to badge when they need action, So that I can see where work is waiting without opening each tab.

Acceptance Criteria:

Given taskService exists but has no React Query hooks When this story lands Then useEventTasks(eventCode) and useMyTasks({critical}) hooks wrap the existing taskService calls (GET /events/{code}/tasks, GET /tasks/my-tasks?critical=true) — frontend only, no backend change (AR8/NFR9).

Given event metrics from useEvent(['metrics','sessions']) and the task hooks When the tab rail renders Then the Speakers & Agenda tab shows a count badge = sessions needing a slot or a content review; the Publishing tab shows a badge when a phase passes validation and is ready to publish; the Communications tab shows a red dot when a comms task is overdue (FR6).

Given no outstanding action for a tab When counts are zero Then that tab shows no badge/dot.

# Phase B — Cockpit

# Story 14.B.1: Cockpit landing layout + 8-step lifecycle spine

As a returning organizer, I want the Cockpit to open with a clear “where is this event” spine, So that I’m re-oriented the moment I land, every time.

Acceptance Criteria:

Given the Cockpit tab (interim Overview content from 14.A.2) When Phase B builds the Cockpit Then it renders three stacked regions top-to-bottom: lifecycle spine → “Needs your attention” → “At a glance” (FR7).

Given getWorkflowProgress/getWorkflowStepNumber and WorkflowProgressBar When the spine renders Then it is a horizontal 8-state stepper: completed states = green check, current = highlighted with “Step N of 8” (FR8), built by reusing the existing helpers/component.

Given event identity lives in Details (§8) When the Cockpit renders Then the Cockpit shows no event identity block — orientation is the header title + spine only.

# Story 14.B.2: “Needs your attention” task cards + Add task

As an organizer, I want a sorted list of what’s due now and next, each with a jump to the right tab, So that the page answers “what now?” without me hunting through tabs.

Acceptance Criteria:

Given useEventTasks/useMyTasks (14.A.3) When the attention region renders Then it shows a card per open task, sorted overdue → due-soon → upcoming, each with a colour strip (red overdue / amber due-soon / green comfortable), task name, a due chip (“Overdue · 3 days” / “Due in 4 days” / “Locks in 6 days”), the assigned-organizer avatar, and a deep-link button to the relevant tab (“Open Communications →”, “Open Publishing →”) (FR9).

Given the attention region When the organizer clicks “＋ Add task” Then a custom task is created via the existing taskService create call and appears in the list (FR11).

Given a deep-link button When clicked Then the page switches to the target tab (and sub-view where applicable) without a route change.

Given the task list is empty (no open tasks for this state) OR the task fetch fails When the attention region renders Then an empty case shows a friendly “You’re all caught up — nothing needs your attention right now” state (not a blank region), and a fetch error shows an inline error + retry (the rest of the Cockpit — spine, metrics — still renders).

Given the “＋ Add task” create call fails When the organizer submits Then the error is surfaced inline (no silent failure), the dialog stays open with the entered values, and no phantom card is added to the list.

No forward dependency on Phase C. Deep-link targets are addressed against the sub-view mechanism that already exists today (EventSpeakersTab already has kanban/table/sessions sub-views), not the renamed Pool/Agenda/Slots toggle that Phase C (14.C.1) formalizes. Use a stable sub-view key (e.g. 'pool' | 'agenda' | 'slots') that maps to the current sub-views now and is preserved by 14.C.1’s relabel — so 14.B.2/14.B.5 are correct whether or not Phase C has landed. 14.C.1 adopts the same keys rather than introducing new ones.

# Story 14.B.3: Per-card completion-signal model (done cards disappear)

As an organizer, I want a card to vanish the moment its work is actually done, So that the Cockpit only ever shows what’s genuinely left.

Acceptance Criteria:

Given AR3 / spec §12.1, the Cockpit must show a card only while it is still open When the completion-signal registry is implemented Then every card type has a defined “done” detector: task-backed → hide when status === 'completed'; data-derived → a named predicate (hide “N sessions need a slot” when sessions.filter(s => !s.startTime).length === 0; hide “review submissions” when no session is awaiting review; hide “outstanding presentations” when sessionsWithMaterialsCount === totalSessionsCount; hide “fill the pool” when acceptedCount >= minSlots); workflow-action → hide when the underlying field/state changes (e.g. topicCode set; workflowState advanced) (FR10).

Given a card whose predicate is satisfied When the Cockpit re-renders Then that card no longer appears in the attention list.

Given the registry When unit-tested Then each predicate is covered by a passing test for both its open and its done state.

Given the §12.1 exhaustiveness decision (Nissim, 2026-06-13 — full table required) When Phase B starts Then a complete card-by-card table — card → completion predicate → data source — covering EVERY card in the prototype’s STATES map is enumerated as a prerequisite to building 14.B.3 (not filled in lazily). Every card resolves to one of the four typed detectors with a concrete predicate/data source; no card is left as “no signal yet.”

Given the venue-booking card (AR4 — RESOLVED) When it is added to the table Then it is task-backed by the existing seeded Venue Booking task (trigger TOPIC_SELECTION, due −90d): shown in the early window, hidden when status === 'completed'. No new backend; the annual forward-planning framing is deferred (not a card in this epic).

# Story 14.B.4: Event-day virtual cards (Start Presentation / Live Control)

As an organizer on event day, I want the live controls surfaced as urgent cards exactly when they matter, So that they’re one tap away on the day but invisible the other 99% of the time.

Acceptance Criteria:

Given the live controls today live off-page (the /organizer/events/:eventCode/live-control route) and are not in the page header When workflowState is AGENDA_PUBLISHED or later Then two virtual attention cards appear at the top of the Cockpit attention list — “🔴 Start the presentation” and “📡 Open Live Control” — styled urgent, due “Now · event is live” (FR12, gate = AGENDA_PUBLISHED onward per the 8-state reconciliation).

Given an event-day card When clicked Then it navigates to the existing live-control / presentation surface (no new backend).

Given workflowState is before AGENDA_PUBLISHED When the Cockpit renders Then the event-day cards are absent.

Given event-day cards are live actions, not tasks When the completion model (14.B.3) runs Then they have no “done” state and persist while in the window.

# Story 14.B.5: At-a-glance metric tiles (clickable deep-links)

As an organizer, I want four headline metrics I can click straight through to, So that I can both read the state at a glance and jump to act on it.

Acceptance Criteria:

Given useEvent(['metrics','registrations','workflow']) (confirmedCount, spotsRemaining, waitlistCount, confirmedSpeakersCount, sessionsWithMaterialsCount, totalSessionsCount, maxSpeakerSlots) When the “At a glance” region renders Then four tiles show: 🎟️ Registrations (confirmedCount / registrationCapacity, % filled, waitlist), 🎤 Speakers (confirmedSpeakersCount / maxSpeakerSlots), 📋 Materials (sessionsWithMaterialsCount / totalSessionsCount), 🗓️ Agenda (sessions slotted / total) (FR13).

Given a metric tile When clicked Then it deep-links: Registrations → Registrations tab; Speakers → Speakers & Agenda · Pool; Materials → Speakers & Agenda · Agenda; Agenda → Speakers & Agenda · Slots.

Given Phase C may not have landed yet (no forward dependency) When a tile deep-links into a Speakers & Agenda sub-view Then it targets the existing sub-view via the stable key ('pool' | 'agenda' | 'slots') that maps to today’s kanban/table/sessions sub-views — so the deep-link is correct before and after 14.C.1’s relabel (same keys, see 14.B.2 note).

# Phase C — Speakers & Agenda

# Story 14.C.1: Tab summary bar + Pool / Agenda / Slots sub-view toggle

As an organizer, I want one Speakers & Agenda tab with three clearly-named sub-views, So that the pool, the agenda, and slotting are one place instead of four scattered tools.

Acceptance Criteria:

Given EventSpeakersTab already has three sub-views (kanban / table / sessions) When the tab is reworked Then a summary bar (accepted/min progress, acceptance rate, “Add speakers”) sits above a 3-way sub-view toggle labelled Pool · Agenda · Slots (FR14). And the toggle reuses the stable sub-view keys ('pool' | 'agenda' | 'slots') that 14.B.2/14.B.5 already deep-link to (mapping to today’s kanban/table/sessions) — this is a relabel, not a new key set, so existing Cockpit deep-links keep working. And the sub-view selection is preserved when the organizer arrives via a Cockpit deep-link (e.g. Materials → Agenda).

# Story 14.C.2: 4-phase speaker kanban with state chips, your-move sort, declined strip

As an organizer, I want the speaker board grouped into four phases with each card showing its exact state, So that I see the progression funnel and whose move it is without 8 columns of noise.

Acceptance Criteria:

Given SpeakerStatusLanes renders 8 lanes (one per state) today When the Pool sub-view is rebuilt Then it shows 4 phase columns — Sourcing (IDENTIFIED·CONTACTED), Inviting (READY·INVITED), Content (ACCEPTED·CONTENT_SUBMITTED), Confirmed (QUALITY_REVIEWED) — and each card keeps its exact 8-state chip (FR15).

Given cards within a column When rendered Then “your move” (organizer-action) cards get an accent left border and sit at the top; below a faint “waiting on speaker” divider sit the blocked-on-speaker cards (FR16).

Given a QUALITY_REVIEWED speaker in the Confirmed column When they have no slot Then the card shows “⚠ Needs a slot →” linking to the Slots sub-view; slotted speakers show ✓ + their time (FR17).

Given declined speakers When the board renders Then DECLINED is a collapsible bottom strip (“▸ Declined (n)”, collapsed by default), not a column (FR18).

Given any card When the organizer clicks it Then the existing SpeakerDetailDrawer (Details · History · Content + primary-action surface) opens unchanged (FR21).

# Story 14.C.3: Workflow-safe kanban drag grammar

As an organizer, I want dragging a card forward to open the same confirmation as its button, advancing exactly one step, So that a drag can never silently provision an account or fire an email.

Acceptance Criteria:

Given the 4-phase board and the ADR-009 8-state SpeakerWorkflowService allow-list When a card is dragged forward across a column boundary Then it invokes the same handler as the card’s primary-action button — opening the relevant confirm/modal (log-outreach, promote, send-invitation) — and never auto-commits (FR19, NFR1, AR6). And it advances exactly one transition (dropping IDENTIFIED on Content must not fire three steps).

Given the two within-pair advances (Identified→Contacted, Ready→Invited, Accepted→Content-submitted) When the organizer triggers them Then they happen via the card button and re-sort the card inside its column; only cross-column steps are a drag (FR19).

Given a backward drag When attempted Then only the single legal back-transition (QUALITY_REVIEWED → CONTENT_SUBMITTED) or the Decline/Override affordance is allowed; any other drag snaps back (FR20).

# Story 14.C.4: Agenda sub-view — session table with slot summary + jump

As an organizer, I want an editable session list that tells me how many slots are still open, So that I can manage the agenda and step straight into slotting.

Acceptance Criteria:

Given the existing SpeakersSessionsTable When the Agenda sub-view renders Then it shows the editable session list (title, speaker, slot chip, materials status, edit) and a “N of M need a slot” summary (FR22).

Given the summary When the organizer clicks “🧩 Arrange slots →” Then the tab switches to the Slots sub-view.

# Story 14.C.5: Slots in-tab — 2-column rework + retire the separate route

As an organizer, I want slot assignment inside the Speakers & Agenda tab, So that I’m not bounced to a separate full-page route just to place sessions.

Acceptance Criteria:

Given DragDropSlotAssignment is a 100vh 3-column layout opened via the dedicated /organizer/events/:eventCode/slot-assignment route (SlotAssignmentPage) When it is reworked Then it becomes a 2-column layout — left = unassigned-sessions tray (drag source), right = the timeline (drop targets; structural moderation/break slots shown non-droppable; hover shows preference-match %) — with the old right-hand “Quick actions” hoisted into a top action bar (🧱 Generate structure · ✨ Auto-assign · 🗑️ Clear all timings + summary “Total 6 · Assigned 4 · Pending 2”) (FR23, UX-DR7).

Given the 2-column layout no longer needs full viewport height When it mounts Then it renders in-tab as the Slots sub-view with the 100vh/viewport-lock removed, no overlay, and the separate /slot-assignment route + SlotAssignmentPage removed (AR5).

Given the route is retired, every in-app navigator to /slot-assignment must be repointed to the in-tab Slots sub-view (none may become a dead navigation) — specifically:

• ValidationDashboard.tsx:91 (navigate(.../slot-assignment) from the “N sessions not yet slotted” Publishing validation row) → switch to Speakers & Agenda · Slots.
• EventSpeakersTab.tsx:325 (plain navigate(.../slot-assignment)) → switch to the Slots sub-view (in-tab, no route change).
• EventSpeakersTab.tsx:266 (navigate(.../slot-assignment?speakerId=${speaker.id})) → switch to the Slots sub-view carrying the speaker context the ?speakerId= query param used to forward (so a QUALITY_REVIEWED “⚠ Needs a slot →” jump still focuses that speaker’s session — FR17).
• The callbacks that feed those handlers — SpeakerStatusLanes.tsx:120 (the “needs a slot” action on a QUALITY_REVIEWED card) and the SpeakerDetailDrawer.tsx:266 slot button — must invoke the in-tab sub-view switch via the same wiring, not a route navigation. When any of those actions is triggered Then the page switches to Speakers & Agenda · Slots in-tab (no route change, speaker context preserved where applicable) — verified by a test per call site.

Given an external bookmark/link to the old /slot-assignment route (incl. a stale ?speakerId=) When opened Then it redirects to the event’s Speakers & Agenda · Slots sub-view (preserving the speaker context if present), so old links never dead-end.

# Phase D — Registrations

# Story 14.D.1: Registrations header — count, capacity, exports, enrol

As an organizer, I want the registrations header to show capacity at a glance with the exports and enrol action beside it, So that the actions that act on registrations live next to the registration data.

Acceptance Criteria:

Given the Registrations tab (existing EventParticipantsTab) When it renders Then the tab label shows a subtle muted count (e.g. “Registrations 140”), not a heavy badge (FR24). And the header shows an active-count chip + a capacity bar (“128/180 confirmed, 12 on waitlist”, red when full) + an action row with Name badges (XLSX), Name badges (DOCX) (existing exportParticipantsXlsx/Docx), and 👥 Enrol organizers & partners (FR25).

Given “Enrol organizers & partners” currently lives in EventOverviewTab (enrollStakeholders()) When Phase D lands Then it is moved into the Registrations header and removed from the (now-Cockpit) Overview content (FR25, FR39 cross-ref).

# Story 14.D.2: Registrations filters + table row actions

As an organizer, I want to search and filter registrants by status, So that I can find the right people and act on their registration.

Acceptance Criteria:

Given EventParticipantTable + RegistrationActionsMenu When the filters render Then there is a debounced search (name/email/company) and a status segmented control (All · Confirmed · Registered · Attended · Cancelled · Waitlisted) (FR26).

Given a table row When the actions menu opens Then it offers Resend confirmation (REGISTERED only), Cancel, Delete — via the existing RegistrationActionsMenu (FR27).

# Story 14.D.3: Waitlist as a filter (queue-ordered + inline promote)

As an organizer, I want the waitlist to be the “Waitlisted” filter rather than a separate table, So that there is one list and one mental model.

Acceptance Criteria:

Given the waitlist is a separate WaitlistSection accordion today When the “Waitlisted” status filter is selected Then the main list swaps to queue-ordered rows (#1, #2, …) with an inline “Promote” action (reusing promoteFromWaitlist), and the separate accordion is removed (FR28).

Given a waitlisted row When “Promote” is clicked and confirmed Then the registrant is promoted and the queue re-numbers.

# Story 14.D.4: Registrations pagination / virtualization

As an organizer, I want the large participant list to render quickly, So that ~200 registrants don’t make the tab sluggish.

Acceptance Criteria:

Given the participant table is not virtualized today and ~200 rows render sluggishly (NFR3) When the list renders Then it is paginated (“Showing 1–25 of 140”) or virtualized.

Given the beta-first/dual-serve constraint (AR9) When pagination is implemented Then it is client-side over the existing list payload by default; if a server-side paginated param is introduced it is optional and the old www frontend (which ignores it) keeps working.

Given boundary cases (zero registrants; a filtered/searched result set smaller than one page; the last partial page; the active filter changing while on page > 1) When the list re-renders Then the counter reads correctly (“Showing 0 of 0” / “Showing 1–7 of 7”), pagination resets to page 1 on a filter/search change, and no empty trailing page is shown.

# Phase E — Communications

# Story 14.E.1: Communications tab — 4-audience switch with Newsletter + Registrant audiences

As an organizer, I want one Communications tab where I pick an audience and compose, So that all outbound email is one surface instead of scattered tabs.

Acceptance Criteria:

Given Newsletter and Registrant Notices are separate tabs today (EventNewsletterTab, EventRegistrantNoticesTab) When the Communications tab is built Then it presents one compose surface with an audience switch over 4 audiences (📰 Newsletter subscribers · 🎟️ Event registrants · 🎤 Speakers · 🏛️ Venue & Caterer), and the form adapts per audience (FR29).

Given the common compose form When any audience is active Then it offers template select, preview-language picker, preview iframe, and a send confirm dialog showing recipient count + template + event title (FR34).

Given the common compose form (applies to ALL four audiences — 14.E.1/14.E.2/14.E.3) When the recipient set is empty (e.g. no active registrants / no speakers / unconfigured venue contact), OR a send call fails, OR a send is in flight Then the Send action is disabled with a reason when there are zero recipients; a failed send surfaces an inline error + retry without losing the composed content; and the button shows a pending/disabled state during the request so a double-click can’t double-send (NFR1 — no silent/duplicate consequential action).

Given the Newsletter audience Then it reuses the existing newsletter behaviour (global list, NEWSLETTER template, organizer-only test-mode, Send Newsletter + Send Reminder, send-history table + retry) via the existing hooks (FR30).

Given the Event-registrants audience Then it reuses the existing registrant-notice behaviour (REGISTRANT_NOTICE template, sent in each registrant’s own language, organizer-only preview picker, single send, no history) (FR31). And the old standalone Newsletter and Registrant Notices tabs are removed.

# Story 14.E.2: Venue & Caterer audience moved into Communications

As an organizer, I want venue and caterer coordination to be a Communications audience, So that it lives with the other outbound email rather than in its own tab.

Acceptance Criteria:

Given venue/catering is the standalone EventVenueTab (VenueCoordinationComposer) today When Phase E lands Then the 🏛️ Venue & Caterer audience composes to venue + caterer contacts with the VENUE_COORDINATION template (booking, headcount, setup) and Reply-To = configured coordinator, reusing venueCoordinationService (FR33). And the standalone Venue tab is removed.

# Story 14.E.3: Speakers audience — wire the existing bulk-reminder hook

As an organizer, I want to send bulk speaker comms (deadline reminders, logistics, thank-you) from Communications, So that I stop sending these ad-hoc from my own mail client.

Acceptance Criteria:

Given useSendReminder exists in useSpeakerPool.ts but is wired to no UI When the 🎤 Speakers audience is built Then it surfaces bulk speaker comms (content-deadline reminder, logistics & arrival, thank-you) using the existing useSendReminder hook — surfacing, not building, backend (FR32, NFR9).

Given a bulk send When the organizer sends Then the send-confirm dialog (recipient count + template + event title) is shown first (NFR1).

Given 1:1 invitations and per-speaker reminders Then they stay on the speaker card in Speakers & Agenda (workflow-bound, 1:1) — not moved here.

# Phase F — Config cluster + remaining tabs

# Story 14.F.1: Wrap-up tab — photos + thank-you notes, locked until live

As an organizer, I want a single post-event Wrap-up tab that’s hidden until the event is live, So that post-event tools don’t clutter the page during planning.

Acceptance Criteria:

Given Photos and Appreciation are separate tabs today (EventPhotosTab, EventAppreciationTab) When the Wrap-up tab is built Then it contains Photos (upload via 3-phase presigned PUT, grid, delete-with-confirm — reusing useEventPhotos/useUploadEventPhoto/useDeleteEventPhoto) (FR36) and Thank-you notes (per-note quote + author, ★ Feature toggle for the public marquee, disabled for anonymous notes — reusing useEventThanks/useSetThanksFeatured) (FR37).

Given the relevance map (14.A.1) When workflowState is before EVENT_LIVE Then the Wrap-up tab is dimmed + 🔒 and non-interactive; from EVENT_LIVE onward it is active (FR5).

Given the “slides are online” communication Then it is not duplicated on Wrap-up — it is a Cockpit task that deep-links to Communications.

# Story 14.F.2: Details tab — identity + topic, with removals

As an organizer, I want the event’s identity and topic on a dedicated Details tab next to Settings, So that set-once identity doesn’t compete with the Cockpit’s “what now?”.

Acceptance Criteria:

Given event identity is edited via a modal (EventForm from openEditModal) today When the Details tab is built Then it shows in-tab: Theme image (replace / ✨ AI-generate), Title + Description (+ ✨ AI-generate description), the selected Topic chip + “Change topic” (opens the Topic overlay, 14.F.3), and When & where (date & start time, event type, registration deadline, venue name, address) (FR38).

Given the old Overview/Details surface When the Details tab lands Then “Preview public page” is removed (Publishing already has a live preview) and “Enrol organizers & partners” is absent here (moved to Registrations in 14.D.1) (FR39).

Given ✨ AI-generate is existing capability (RESOLVED by code 2026-06-13 — Story 10.16: endpoints /events/{code}/ai/description, /ai/theme-image, /ai/theme-image/apply; hooks useAiGenerateDescription / useAiGenerateThemeImage / useAiApplyThemeImage; AiAssistDrawer already used by EventOverviewTab + EventForm) When the Details tab surfaces the AI-generate actions Then it recomposes the existing AiAssistDrawer / hooks onto Details — no new backend, NFR9-safe. This is a re-surfacing, not a new capability.

As an organizer, I want choosing a topic and brainstorming speakers to be one focused overlay from Details, So that setup is a single continuous gesture without a page change.

Acceptance Criteria:

Given the topic experience is the standalone /organizer/topics route (TopicManagementPage → TopicBacklogManager + SpeakerBrainstormingPanel) today When “Change topic” is clicked in Details Then a focused overlay opens (not a route change), reusing TopicBacklogManager content in State A: filters on a horizontal top bar (search, category, status, sort, list/heat-map toggle, ＋ New topic) + a single card grid where each card folds in its detail (title, staleness chip + colour-coded border, category, last-used + usage count, inline similarity warning) (FR40, AR7).

Given a topic card in State A When rendered Then card actions are Select for event · Edit · 🗑️ Delete (delete disabled when usageCount > 0); a too-recent (red) topic shows “Select anyway…” + keeps the override/justification dialog (FR41).

Given a topic is selected When State B renders Then the topic pins to the top as a confirmed banner and the view becomes speaker brainstorming (SpeakerBrainstormingPanel: add-a-potential-speaker form + pool list with status chips

• “Promote” on CONTACTED speakers) with a footer “Skip for now” / “Continue to outreach →” that lands on Speakers & Agenda · Pool (FR42).

# Story 14.F.4: Publishing & Settings finalization (placement, removals, guard)

As an organizer, I want Publishing and Settings to sit correctly in the new IA with their small redesign deltas applied, So that the config cluster is complete and safe.

Acceptance Criteria:

Given the existing EventPublishingTab mounted by the Phase A shell When Phase F finalizes it Then Publishing keeps its validation checklist, publishing-phases timeline (validation-gated publish action), and live preview, and its “ready to publish” state feeds the Phase A Publishing badge (FR35).

Given the existing EventSettingsTab When Phase F finalizes it Then Settings keeps Event moderator (OrganizerSelect), Registration capacity (blank = unlimited; ≤ venue capacity), Session Q&A (enable toggle, open-trigger, days-open; Save/Close-now/Open), Teaser images (n/10 with per-image “show after”), and a Danger zone — Cancel event (notifies registrants) and Delete event (disabled when realAttendeeCount > 0) (FR43). And logistics (venue/caterer) is confirmed absent from Settings (it is the Communications Venue & Caterer audience from 14.E.2).

# Story 14.F.5: Cockpit replaces interim Overview — remove the old Overview content

As an organizer, I want the Cockpit to be the sole landing surface, So that there is no leftover Overview duplicating identity, metrics, or quick-actions.

Acceptance Criteria:

Given Phase A mounted today’s EventOverviewTab content as the interim Cockpit, and Phases B/D moved its pieces (metrics → Cockpit tiles; enrol → Registrations; identity → Details) When Phase F completes Then the interim Overview content is removed and the Cockpit (14.B.*) is the only landing tab — no duplicated identity block, metrics, topic display, or quick-actions remain (FR3, FR7 cross-ref).

# Phase G — Mobile

# Story 14.G.1: Mobile bottom nav + More sheet

As an organizer on my phone, I want the four day-to-day destinations in a bottom bar and the rest behind “More”, So that the 8-tab IA fits a phone without cramming.

Acceptance Criteria:

Given EventPage.tsx already uses MUI BottomNavigation on mobile When the mobile nav is reshaped Then the bottom bar holds Cockpit · Speakers · Registrations · Communications (with badges/dots) and a ⋯ More entry opens a bottom sheet with Publishing · Wrap-up · Details · Settings (FR44).

Given the relevance map When workflowState is before EVENT_LIVE Then Wrap-up shows 🔒 in the More sheet and is non-interactive.

# Story 14.G.2: Mobile Cockpit

As an organizer checking in on the go, I want the Cockpit to adapt to a phone, So that “what now?” is readable and tappable on a small screen.

Acceptance Criteria:

Given the desktop Cockpit (Phase B) When rendered on mobile Then the lifecycle spine collapses to a “Step N/8” bar, task cards stack full-width, and the four metric tiles render 2-up and remain tappable deep-links (FR45).

# Story 14.G.3: Mobile Slots — tap-to-assign

As an organizer assigning slots on a phone, I want to tap a session then tap a slot, So that I’m not fighting drag-drop on a touchscreen.

Acceptance Criteria:

Given the 2-column Slots sub-view (14.C.5) When used on touch Then tapping an unassigned session lights up the empty slots; tapping a slot places the session there (FR46) — drag-drop is replaced by tap-to-assign on touch.

# Story 14.G.4: Mobile Registrations — tables to cards

As an organizer on my phone, I want registrants as cards with an overflow menu, So that the table is usable on a narrow screen.

Acceptance Criteria:

Given the Registrations table (Phase D) When rendered on mobile Then each registrant renders as a card with a ⋯ overflow exposing the row actions (FR47).

# Open Questions

All three open questions are RESOLVED (2026-06-13). Kept here as a decision record.

1. How do we know the venue is “booked”? (Story 14.B.3 / AR4) — ✅ RESOLVED. The card is task-backed by the already-seeded Venue Booking task (V22: trigger TOPIC_SELECTION, due −90 days, carries a status) — it shows per-event in the early window and disappears when that task is marked completed. No new field, no derived record, no backend change. The annual “book the next ~2 years ahead” framing is deferred — not modelled as a separate card in this epic. (Decision: Nissim, 2026-06-13. See AR4 + Story 14.B.3.)

2. Is “✨ AI-generate” for the theme image and description new or existing? (Story 14.F.2) — ✅ RESOLVED (existing). Confirmed against the code: AI-generate is existing capability (Story 10.16). The endpoints /events/{code}/ai/description, /events/{code}/ai/theme-image, and /ai/theme-image/apply exist; the frontend hooks useAiGenerateDescription / useAiGenerateThemeImage / useAiApplyThemeImage and the AiAssistDrawer are already wired into EventOverviewTab + EventForm. Story 14.F.2 recomposes these onto the Details tab — no backend work, the frontend-only / beta-first constraint holds. (Resolved by code inspection, 2026-06-13.)

3. Does the §12.1 completion-signal table need to be exhaustively enumerated before Phase B starts? — ✅ RESOLVED (full table first). Yes — the full card-by-card table is a prerequisite to Phase B. Before building Story 14.B.3, enumerate every card in the prototype’s STATES map to a card → completion predicate → data source row, each resolved to one of the four typed detectors (no card left as “no signal yet”). The four typed detectors + named predicates are the method; the complete enumeration is the deliverable that gates Phase B. (Decision: Nissim, 2026-06-13. See Story 14.B.3 ACs.)

# Post-Implementation Follow-ups — revisit after ALL stories are merged

Incidental, low-severity items surfaced during the Phase A code review (the 8-tab shell, 2026-06-13). Each is bounded by an interim heuristic that a later phase supersedes — listed here (not in throw-away deferred-work) so they are checked off when the epic is complete. None blocks any story.

• Comms-overdue dot under-matches venue/caterer tasks — web-frontend/src/components/organizer/EventPage/tabBadges.ts (COMMS_TASK_PATTERN). The regex was deliberately narrowed to clearly comms-owned names (newsletter / registrant-notice / Teilnehmer-Info) to avoid false positives like “Book the venue”. Consequence: an overdue Venue Booking / Catering Coordination task does not raise the Communications dot, even though Venue & Caterer is a comms sub-surface. Phase E (14.E.2) should fold venue/caterer tasks into the audience model and re-derive the dot from a first-class category rather than a name heuristic — then this regex can be removed. (Review: Edge-case hunter M3.)
• Speakers attention-badge can double-count one speaker — tabBadges.ts (computeTabBadges): speakers = sessionsNeedingSlot + pendingMaterialsCount, so a speaker with an unslotted session who also owes materials counts in both terms. Intended as an “open items” count, not a headcount. Phase B (Cockpit / FR16–FR17) should confirm whether a true per-speaker headcount is wanted and, if so, de-dupe by speaker. (Review: Blind #1 / Edge L5.)
• Unknown/absent workflowState leaves Wrap-up active (not locked) — web-frontend/src/utils/workflow/workflowState.ts (getTabRelevance). By frozen design (“never hide a tab”; unknown → active) and harmless because workflowState is always present on /organizer/events/:eventCode. Accepted-by-design, not a fix — revisit only if a real legacy/empty-state event is ever observed exposing post-event tools early. (Review: Edge-case hunter H1.)