Stage zero coverage checkpoint

Positioning Interrogation Coverage Checkpoint - Draft Stonk

Round 1 covered every required positioning interview area. This checkpoint asks you to confirm the assembled scope before the parent $positioning loop writes the interrogation handoff and builds the framework-selection alignment page.

Status: consumed by round 3; user feedback raised a real-money, brokerage API, prize-pool, and gambling/advice boundary follow-up.

Coverage Summary

Source: consumed round-1 YAML at research/_working/interrogation-positioning-r1.yaml, checked against README.md, concept.md, research/icp.md, research/competitive-analysis.md, and research/journey-map.md.

Target Segment

confirmed

Positioning should primarily speak to U.S. finance-curious social retail players. Friend groups, fantasy-sports-adjacent players, and college finance clubs remain important wedges and contexts.

Competitive Alternatives

confirmed with user wording

The actual alternative set should foreground group chat, spreadsheets, Robinhood or brokerage/watchlist behavior, fantasy sports mental models, and the familiar option of doing nothing after the argument fades.

Value Wedge

confirmed

The wedge is a fast social game that makes market instincts visible and comparable: learn together, have fun with friends, and turn stock opinions into a fair shared scoreboard without real-money trading.

Mode

confirmed

This run should stay in market-positioning mode because the repo has concept, ICP, competitive, and journey evidence but no real customer feedback, interviews, production behavior, or analytics.

Category Frame

confirmed

The frame should remain a social fantasy stock draft or fantasy stock game, anchored in "fantasy football, but for stocks" and the approved no-money, no-prize, no-advice posture.

Customer Language

confirmed as preferred phrasing

User-provided anchor: "I want to learn how to trade and have fun with my friends while doing so. Make making money social and learn together."

Language Boundary

Copy Risk To Resolve In Framework Research

The words "trade" and "making money" are useful because they sound closer to the user's desired outcome, but the canonical positioning should not imply brokerage behavior, investment advice, real-money winnings, paid contests, or gambling. The safer research instruction is: preserve the social learning and friendly competition intent, while translating risky phrasing into entertainment-first language.

Readiness Matrix

Interview Area Coverage State Confidence What Would Change It
Target segment Covered by confirmed assumption from research/icp.md. High User elevates clubs, educators, creators, or fantasy sports players above the consumer social retail player.
Competitive alternatives Covered by confirmed assumption and user answer: group chat, spreadsheet, Robinhood, fantasy sports. Medium-high User removes brokerage/watchlist behavior, fantasy sports, or do-nothing inertia from the alternative set.
Value wedge Covered by journey-map evidence and user language about learning and having fun with friends. Medium-high User prefers serious skill-building, school curriculum, or trading practice over social game payoff.
Mode Covered by confirmed market-positioning override. High Real customer feedback or shipped-product evidence appears.
Category frame Covered by README, competitive analysis, and user boundary to avoid gambling. High User wants to intentionally explore paid contests, prizes, or betting-adjacent framing.
Customer language Covered, with a copy-risk caveat for "trade" and "making money." Medium User supplies real quotes, interview notes, or alternate phrasing that avoids risky implications.

Checkpoint Gate

Confirm Coverage Or Flag Gaps

Is this coverage complete enough for the next $positioning run to write the interrogation handoff and build the framework-selection alignment page?

Compile Responses

Compile YAML and paste it into a fresh Codex session invoking $positioning. If coverage is confirmed, the parent will write the handoff and proceed to the framework-selection approval page on the next run.

No YAML compiled yet.