Most social games ask users to leave the conversation.
That creates friction. The interesting question is what works when the board, move, challenge, prediction, and audience stay inside the thread.
Timeline-Native Experiences
ThreadPlay is the lab. Battle Dinghy is the first artifact. The broader category is timeline-native UX: experiences that use the thread itself as interface, state, distribution, and spectator surface.
Category Thesis
Social platforms already contain identity, distribution, conversation, rivalry, spectators, status, and asynchronous turn-taking. ThreadPlay treats those as product primitives.
That creates friction. The interesting question is what works when the board, move, challenge, prediction, and audience stay inside the thread.
Replies can become moves. Posts can become game-state updates. Spectators can react, predict, challenge, and enter the loop without installing another app.
A lab for timeline-native experiences: games, predictions, challenges, wagers, and social mechanics designed to run directly inside platforms like X.
A Battleship-style timeline-native strategy game. The public page should explain the rules, challenge flow, board state, and why the thread is both game surface and distribution channel.
ThreadBookie and related concepts should lead with prediction and challenge mechanics before betting language. The point is market-like interaction inside social context.
These repos support interaction testing: posts, replies, turn markers, board embeds, spectators, and persistent public state.
Next Build Pass