UC_4.9.2: Pod Mentorship Module (SIM)

---

Document References

---

1. Overview

⛔ [BLOCKED — pending design] No wireframe file for the SIM locked state exists in References/Wireframe/ yet. The two files in References/Wireframe/Stage 2/Community & Live Broadcast/ (Community (with data).webp, Community (no data).webp) both show the LIVE variant of this card. The BA will add the SIM screenshot to that folder; this reference must be replaced with the real path once the file is available. Ref: QnA_init_docs.md QN-4.9.2-09.

2. Trigger

The trader navigates to the Community page via the Community tab in the persistent sidebar (Ref: UC_4.1.2 §2 Screen Description) → the My POD card mounts.

3. Pre-conditions

• The user is authenticated and is on the Community page.
• The account is a SIM (Evaluation) account at Level 0.

4. Post-conditions

• The My POD card is rendered in its locked state. It occupies its full slot in the Community page grid (Ref: BR_4.9.2.2).
• No pod membership is created, requested, or queued. The trader's pod eligibility is unchanged by anything they can do on this card.
• The account remains a SIM account. Once it leaves SIM, this UC no longer applies and ownership of the card passes to UC_4.14.2 (Ref: BR_4.9.2.3).

5. Basic Flow

1. The Community page renders. The My POD card mounts in its grid slot.
2. The frontend renders the locked state directly, without issuing any request. GET /community/my-pod is not called for a SIM account (Ref: BR_4.9.2.4).
3. The card displays the empty-state title You're not in a POD and, beneath it, the supporting line Pass the Associate Track to Unlock (Ref: BR_4.9.2.2).
4. The card displays the Join a POD control in a Disabled state. It cannot be activated and performs no action (Ref: BR_4.9.2.1).
5. The card holds this appearance for the whole session. There is no second state, no transition, and no refresh (Ref: BR_4.9.2.4).

6. Alternative Flow

N/A — the card has exactly one state for a SIM account (Ref: BR_4.9.2.4).

7. Exceptional Flow

N/A — the card issues no request, so there is no failure, timeout, or empty-payload path to handle (Ref: BR_4.9.2.4).

8. Business Rules

BR_4.9.2.1: Pod Mentorship Is Not Available to SIM Accounts

Pod Mentorship is reserved for traders at Level 1 and above trading live capital. It is not available to SIM or Evaluation accounts in any form — including read-only viewing of pod information (Source: QnA from clients — STAGE 2: Community & Live Broadcast, row Pod Mentorship / Definition).

For a SIM account this means:

• The trader is never a member of a pod and is never placed on the pod waitlist.
• The trader cannot initiate pod assignment. The Join a POD control is rendered Disabled: it does not respond to activation, navigates nowhere, and issues no request. In particular it does not route to the external join form used on the LIVE side.
• No tooltip, toast, modal, or upsell call-to-action is attached to the disabled control. The reason is already stated permanently on the card by the supporting line (Ref: BR_4.9.2.2), so no additional explanatory element is built.

BR_4.9.2.2: The Card Is Rendered, Never Hidden

The My POD card must not be hidden for a SIM account. Hiding the component would break the Community page grid layout (Source: QnA from clients — STAGE 2: Community & Live Broadcast, row Pod Mentorship / Definition). The card keeps its slot and its dimensions so that the surrounding widgets are not repositioned.

The card renders the standard empty-state design with the following content:

The supporting line replaces the descriptive line shown on the LIVE variant of the empty state; the LIVE description is not rendered for SIM.

⚠️ Open item — wording pending client confirmation. The client's written instruction was to "display a locked text state on the button reading 'Pass the Associate Track to Unlock'", which reads as changing the control's label. The approved design instead keeps the label Join a POD and places that text on the supporting line above it. The BA confirmed the design on 2026-08-10 and the table above follows it; the divergence from the client's literal wording is to be confirmed with the client together with the wireframe. Ref: QnA_init_docs.md QN-4.9.2-02.

BR_4.9.2.3: Scope Boundary — All Pod Behaviour Belongs to UC_4.14.2

This UC owns only the locked appearance of the card while the account is SIM. The moment the account leaves SIM, this UC no longer applies and ownership of the card passes to UC_4.14.2 — Pod Mentorship Module (LIVE) (not yet documented in this repo). The card changes on the next load of the Community page; no real-time push exists for this transition.

The following are named here only to mark the boundary. None of them is behaviour of this card, and none is restated as a rule of this UC: the GET /community/my-pod contract and its leader / members / discord_channel_url / join_form_url payload; the external join form and the asset-class and trading-style preferences it collects; the matching waterfall and the FIFO waitlist; the Pending Assignment state; the pod capacity of one leader plus seven members; the leader and member list rendering with its per-member status indicator; the Enter My POD control and the private Discord pod channel it opens; the trading-plan and induction SLA deadlines; and the carry balance and its monthly vesting.

BR_4.9.2.4: Static Card — No API Call, No Loading State, Single Appearance

The locked state is a constant. It is derived from the account being SIM and depends on no server-side data, so:

• The frontend does not call GET /community/my-pod for a SIM account. No request is issued by this card at any point.
• There is consequently no loading or skeleton state, and no error, timeout, or empty-payload handling for this card. Any page-level loading treatment for the Community page as a whole is owned by the Community page layout, not by this UC.
• The card has exactly one appearance, held for the entire session. It does not vary with elapsed time, with the trader's Discord linking state, or with the state of any other widget on the Community page. No user action available on the card changes it.

9. Screen Description

Related behaviour owned elsewhere: when the trader navigates into the Community screen, the Newsquawk audio stream in the persistent header switches to Off automatically. That rule is owned by BR_4.1.4.4 and is not restated here.

---

Changelog