Field	Value
BA in Charge	Trang Nguyen
Date Created	2026-08-12
Version	v1
Document References	RFQ_ Website and Dashboard Implementation V7.pdf (§Part C: Trader Dashboard Implementation, Key Features — The Desk Manager) · RFQ_ Stack Trading Prop Tech V7.pdf (§3.2 GEKKO_CHATTER event, §3.2.1 The Desk Manager — LLM Commentary Engine) ·`docs/BA/UC_4.1-4.17/dashboard_live/UC_4.12.3/QnA_init_docs.md` (QN-4.12.3-01..05) · UC_4.8.3 (SIM sibling — same engine, LIVE adds 2 events)

UC_4.12.3 — The Desk Manager (LIVE)

1. Overview

Field	Content
ID	UC_4.12.3
Use Case	The Desk Manager (LIVE)
Description	The same optional, LLM-driven "Chatter" widget as the SIM sibling (UC_4.8.3) — a stateless commentary engine (Google Gemini 1.5 Flash 8B, "Gordon Gekko" persona), rendered as stacked UI cards tagged "Discipline pass"/"Discipline fail", delivered asynchronously over `GEKKO_CHATTER`, rate-limited at 10 critiques/hour/user. LIVE reuses the SIM's engine, rate limit, and card-stack UI 100% unchanged (Ref: QN-4.12.3-02, QN-4.12.3-03) — the only difference is the trigger event set: LIVE fires the 13 events shared with SIM plus two LIVE-exclusive events, `DEFENSE_TRIGGERED` and `POD_DYNAMICS`; `STAGNATION` is SIM-only and never occurs on LIVE (Ref: BR_4.12.3.1).
Zapier Flow	—
Zapier Table	—
3rd Party	Google Gemini 1.5 Flash 8B (LLM commentary generation)

References/Wireframe/Stage 2/Dashboard/Dashboard.png The Desk Manager panel, populated — shared visual reference with SIM (Ref: UC_4.8.3 §1).

2. Trigger

A GEKKO_CHATTER WebSocket event arrives while the user is on the screen hosting this widget (Ref: BR_4.12.3.1) — same mechanism as SIM.

3. Pre-conditions

User is on the screen (Ref: UC_4.1.1 §1 Overview) with an active LIVE account.
The account is not locked (no Hard Breach state) and the account's data has not been archived — same condition as SIM (Ref: UC_4.8.3 BR_4.8.3.3).

4. Post-conditions

The widget continues to render new commentary cards as GEKKO_CHATTER events arrive — including cards triggered by the LIVE-exclusive DEFENSE_TRIGGERED and POD_DYNAMICS events — for as long as the pre-conditions in Section 3 hold and the AI Chat feature is enabled.

5. Basic Flow

Backend evaluates trader actions against the LIVE event set — the 13 events shared with SIM, plus the LIVE-exclusive DEFENSE_TRIGGERED and POD_DYNAMICS (Ref: BR_4.12.3.1).
[If the trader's Token Bucket has remaining quota] backend's async worker sends the Master Prompt Payload to the Gemini 1.5 Flash 8B API and, on response, pushes {text, vibe, event_type} over GEKKO_CHATTER — same mechanism as SIM (Ref: UC_4.8.3 BR_4.8.3.1, BR_4.12.3.2).
[If the Token Bucket is exhausted] no commentary is generated or sent for this trigger — no UI feedback of any kind (Ref: BR_4.12.3.2).
Frontend receives the GEKKO_CHATTER payload and renders a new stacked card, styled per the vibe → style-group mapping — same as SIM (Ref: UC_4.8.3 §8 Screen Description, row 3).
The new card is added to the top of the stack; only the 2 most recent cards are visible in the viewport without scrolling — older cards remain reachable by scrolling — same UI behavior as SIM (Ref: BR_4.12.3.3).

6. Alternative Flow

None beyond the boundary cases already covered in SIM's UC_4.8.3 §6 Exceptional Flow, which apply unchanged to LIVE (Token Bucket exhausted, account locked/archived, AI Chat off, Day-0 empty state, LLM delay/failure).

7. Exceptional Flow

Same as SIM — Ref: UC_4.8.3 §6 Exceptional Flow — not repeated here.

LIVE fires the 13 events shared with SIM (UC_4.8.3 BR_4.8.3.1): SESSION_START, LOSS_EVENT, PROMOTION, STOP_HIT, NEWS_HOLD, ORDER_CANCELLED, PAPER_HANDS, TRADE_CLOSED, THE_WHALE, REVENGE_TRADE, THE_CLOCK_WATCHER, SCALP_HUNTER, COMMUNITY_LIVE.

Plus two LIVE-exclusive events: DEFENSE_TRIGGERED and POD_DYNAMICS. Neither occurs on SIM (Source: BA confirmation, 2026-08-13, cross-ref UC_4.8.3 BR_4.8.3.1; RFQ_ Stack Trading Prop Tech V7.pdf §3.2.1 lists 15 events total across both environments).

BR_4.12.3.2: Rate Limiting — Same as SIM

The same Token Bucket algorithm (10 critiques/hour/user) and the same silent-decline behavior on exhaustion apply unchanged to LIVE (Source: BA confirmation, 2026-08-12, QnA_init_docs.md QN-4.12.3-02; Ref: UC_4.8.3 BR_4.8.3.2).

BR_4.12.3.3: Card Stack UI — Same as SIM

The card stack UI behavior (2 cards visible without scrolling, older cards reachable by scroll, no auto-expire, no cap on total stored cards) is unchanged from SIM (Source: BA confirmation, 2026-08-12, QnA_init_docs.md QN-4.12.3-03; Ref: UC_4.8.3 BR_4.8.3.3). Only the event source differs from SIM (Ref: BR_4.12.3.1) — the UI component itself is identical.

BR_4.12.3.4: Per-Event Trigger and Prompt Mapping — LIVE-Exclusive Events

Completes the per-event prompt mapping for the 2 events that are LIVE-exclusive (Ref: BR_4.12.3.1) and therefore excluded from SIM's mapping table (UC_4.8.3 BR_4.8.3.5). Both draw on the same 18-constraint numbering established in that SIM table (Ref: UC_4.8.3 BR_4.8.3.5) — constraint 4 for DEFENSE_TRIGGERED, constraint 8 for POD_DYNAMICS (Source: RFQ_ Stack Trading Prop Tech V7.pdf §3.2.1).

Event	Trigger	Content / Prompt Rule	Note
`DEFENSE_TRIGGERED`	When a trader enters the Drawdown Defense protocol (Flow 4B) — business logic owned by UC_4.15.4 (not yet documented in this repo; dial-recalculation side effect covered inUC_4.12.2 BR_4.12.2.3), not repeated here.	4:"If event_type is DEFENSE_TRIGGERED, act as the Warden who pulled the plug to save his money."	—
`POD_DYNAMICS`	A Pod Leader receiving a bonus or a Pod Member being promoted (Source: RFQ_ Stack Trading Prop Tech V7.pdf §3.2.1).	8:"Apply the Pod Role constraint. If they are the Leader, tell them they finally earned their keep off the backs of their team. If they are a Member, tell them to thank their leader for dragging them across the finish line."	Wording override: BA supplied replacement wording for constraint 8 specific to LIVE's `POD_DYNAMICS` prompt (Ref: `QnA_init_docs.md` QN-4.12.3-05) — the constraint number (8) is unchanged from the original source numbering used throughout UC_4.8.3 BR_4.8.3.5; only the constraint's text is replaced.

9. Screen Description

No.	Field Name	Field Type	Displaying rule / Behaviour rule
1	Commentary card stack	Label	Displaying rule:- Same as SIM — Ref: UC_4.8.3 §9 Screen Description, row 1. Ref: BR_4.12.3.3.Behaviour rule:- Read-only. New cards prepend to the stack as `GEKKO_CHATTER` events arrive — event source includes `DEFENSE_TRIGGERED` and `POD_DYNAMICS` in addition to SIM's shared set (Ref: BR_4.12.3.1).
2	Card text	Label	Displaying rule:- LLM-generated commentary text (`text` field). Same per-event mapping pattern as SIM for the 13 shared events (Ref: UC_4.8.3 BR_4.8.3.5); `DEFENSE_TRIGGERED` and `POD_DYNAMICS` prompt content per BR_4.12.3.4. Overflow: Wrap text.
3	Card style tag	Badge	Displaying rule:- Same as SIM — one of 2 values ("Discipline pass"/"Discipline fail"), derived from `vibe`. Ref: UC_4.8.3 §9 Screen Description, row 3.

SRS: UC_4.12.3 — The Desk Manager (LIVE)