Stage zero follow-up
Round 2 did not pass the coverage checkpoint because the confirmed edits introduced a different product: paid entry, winner-take-all payout, and possible brokerage API execution. This page resolves that boundary before framework selection.
"Yes making money would be implied. Can we not create api connections to brokerages to enable users to make trades based on their picks? Like $100 fantasy draft, with equal allocation across 5 rounds means $20 for each stock picked. Then winner takes all? Is that considered gambling?"
High risk
A $100 paid-entry pool with winner-take-all value has consideration and a prize. Whether it is gambling, a contest, or an illegal lottery depends on state law and how much skill versus chance determines the result. Because stock price movement is external to the player, this should be treated as gambling-adjacent until gaming counsel says otherwise.
High risk
Letting users execute real securities trades from draft picks changes the product from a fantasy game into securities-transaction infrastructure. If Draft Stonk participates in solicitation, execution, order routing, transaction compensation, or handling funds/securities, broker-dealer analysis is required.
Medium to high risk
Copy like "learn how to trade," "make money," "buy this," or "winner takes all" can make users read the product as advice, trading, or betting. Even without trade execution, compensated advice or securities analysis can create investment-adviser questions.
Lower positioning risk
The current approved frame stays materially cleaner: no real-money trading, no prizes, no brokerage links, no account funding, no advice, and scoreboards used for bragging rights, learning-by-play, and social comparison only.
| Source | Why It Matters Here | Positioning Implication |
|---|---|---|
| 31 U.S.C. 5362 | Federal internet-gambling definitions discuss staking something of value on contest or chance outcomes for value, and the fantasy/simulation sports carveout has specific conditions. State law still matters. | A paid stock draft with a prize pool should not be assumed to fit a fantasy-sports carveout. |
| California Penal Code 319 | California's lottery definition includes paid consideration, chance, and distribution of property. | State-level lottery/gambling analysis can be triggered by paid entry plus prize mechanics. |
| SEC Broker-Dealer Registration Guide | The SEC flags securities transaction participation, platforms to trade securities, transaction compensation, and handling funds/securities as broker-dealer analysis factors. | Brokerage API execution is outside the current no-brokerage positioning scope. |
| Investor.gov Investment Adviser Glossary | Investment-adviser status can involve compensation plus investment advice, reports, or analysis about securities. | Draft Stonk should avoid advice-like framing while in the entertainment-first path. |
| Path | Category Frame | Research Mode Impact | What The Next Stage Can Safely Do |
|---|---|---|---|
| No-money fantasy stock draft | Social fantasy stock game for market instincts and bragging rights. | Continue market-positioning with current ICP, competitive analysis, and journey map. | Build framework-selection page using the no-money/no-prize/no-advice boundary. |
| Watchlist or export handoff | Fantasy game with optional user-directed research or watchlist export outside trading flow. | Possible later product extension; still needs careful copy and partner/API review. | Keep current positioning no-brokerage, but record watchlist export as a separate future question. |
| Brokerage API / real trades | Trading-connected finance product, not just a game. | Would require securities counsel, broker/API partner review, and likely a different positioning run. | Stop this positioning path and define a regulated product discovery lane before claims are made. |
| Paid entry / winner-take-all | Paid contest or gambling-adjacent product. | Would require gaming/contest counsel, jurisdiction strategy, age/location controls, terms, tax, and compliance design. | Do not include in current positioning except as an excluded or deferred path. |
Which boundary should the next $positioning stage carry forward?
If brokerage connectivity is mentioned later, what is the permitted scope?
How should framework research handle the user language "learn how to trade" and "making money social"?
Use this open field to add your final boundary, wording, risk appetite, or any question that must be answered before framework selection.
Compile YAML and paste it into a fresh Codex session invoking $positioning. The parent will consume this answer and either build a final coverage checkpoint or continue the interrogation if a regulated path is selected.