Theoryfall.com

What the company appears to be: Theoryfall.com is a self-reported browser-based 3D spatial-reasoning game built around three projections of 3D structures. The author states it was developed using Codex and GPT-5.6-Sol, but no runtime AI is used in gameplay. It is described as a learning experience focused on reconstructing 3D geometry from 2D views.

What changed: The project description indicates this is a solo-built prototype submitted to the OpenAI 2026 hackathon. No prior version or evolution is evidenced; it appears to be an initial build with no prior commercial traction.

Single most important open question: Is there evidence of any measurable learning outcome, user engagement, or product-market fit beyond the author's own claims?

The description states that Theoryfall is a cinematic spatial-reasoning game where players reconstruct 3D structures from three projections (front, top, side). Players place and rotate cube-based pieces to match the given views. It includes a prologue with three levels: Mirror Gate, Blind Side, and Turning Crown.

• Evidenced: The product is described as a browser-native 3D game built with Three.js, React Three Fiber, TypeScript.
• Inferred: The core mechanic involves validating player constructions against projection data.
• Not evidenced: No details on gameplay mechanics beyond the stated levels or how feedback is delivered.

The author positions Theoryfall as a learning experience that bridges the gap between 2D textbook geometry and 3D spatial reasoning. The tagline "A cinematic game where players learn spatial reasoning by reconstructing 3D structures from three projections" reflects this positioning.

• Evidenced: The product is framed as an educational tool for spatial reasoning.
• Inferred: It aims to make abstract mathematical concepts tangible through interactive play.
• Not evidenced: No evidence of prior versions, market testing, or user feedback on effectiveness.

The author describes the target audience as individuals who enjoy geometry and want a more immersive way to learn spatial reasoning. The game is positioned for learners who may struggle with traditional 2D representations of 3D problems.

• Evidenced: The product targets people interested in mathematics, especially geometry.
• Inferred: Likely aimed at students or hobbyists seeking hands-on learning tools.
• Not evidenced: No specific demographics, usage patterns, or customer segments are provided.

The description does not mention any pricing model, monetization strategy, or business model. It is described as a prototype submitted to a hackathon.

• Evidenced: No commercial structure or revenue model is stated.
• Inferred: The project may be in early development and not yet monetized.
• Not evidenced: No information on subscriptions, freemium models, or sales channels.

The author reports building the game using a tech stack including TypeScript, React Three Fiber, Three.js, Cloudflare Workers, D1, XState, and various development tools like Storybook and Vitest. AI was used in development but not during gameplay.

• Evidenced: The project is built with modern web technologies.
• Inferred: The use of AI in development suggests a rapid prototyping approach.
• Not evidenced: No details on scalability, performance metrics, or deployment architecture beyond the tech stack.

The project is described as a hackathon submission and not yet released to users. It has no evidence of revenue, customers, or adoption.

• Evidenced: Submitted to OpenAI 2026 hackathon.
• Inferred: The product is in early development stage.
• Not evidenced: No user data, engagement metrics, or market traction are reported.

The description does not provide any information about competitors or the broader marketplace for educational games or spatial reasoning tools.

• Evidenced: No mention of existing products or competitive landscape.
• Inferred: Likely in a niche space involving STEM education and interactive learning.
• Not evidenced: No comparison to other platforms, tools, or methodologies.

Key risks include:

• Lack of measurable learning outcomes or user feedback
• Solo development may limit scalability or long-term maintenance
• Prototype nature implies unproven market fit or commercial viability

• Evidenced: The project is a solo-built hackathon submission.
• Inferred: Risk of limited product-market fit without external validation.
• Not evidenced: No evidence of risks related to funding, team expansion, or long-term strategy.

1. What specific learning outcomes have you observed from playtesting?
2. How do you plan to validate the educational value of this experience?
3. Have you considered how to scale beyond a single developer?
4. Is there any intention to monetize or expand the product beyond its current scope?
5. What are your plans for user feedback and iteration?