Archive position — measured, not model output
0 likes on Devpost
2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #5,172 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be
Mastery is a self-reported question-first learning environment that uses AI to help users explore concepts from texts through interactive questioning, concept mapping, and teach-backs. It integrates with Obsidian for knowledge export and is built using OpenAI's GPT models, Codex, React, Supabase, and PostgreSQL.
What changed
The project pivoted from a branching reader to a core loop focused on transfer checks and teach-backs after realizing that reading alone does not lead to retention. The pivot was driven by time constraints but also reflects a stated belief in active recall and explanation as the key to learning.
Single most important open question
Is there evidence of user traction, revenue, or adoption beyond the self-reported project description? The description lacks any data on usage, customers, or monetization.
What The Product Actually Is
The description states that Mastery is a question-first learning environment. It allows users to import text, select confusing parts, and ask questions. The system responds with explanations and builds a concept map. Concepts are verified through transfer checks and teach-backs, where an AI student (Milo) evaluates the user’s ability to explain the concept in their own words.
The process includes:
- Streaming tutor explanations
- Mapping concepts into nodes
- Generating transfer checks
- Playing Milo, an AI student who grades teach-backs
- Identifying gaps via dashed ghost nodes on the map
It also supports exporting concepts to Obsidian with full evidence history and wiki-links that mirror the concept map.
Inference The product is built around a learning loop involving questioning, mapping, testing understanding, and retention. It is not a general-purpose note-taking tool but a structured study environment.
Positioning & Claim Evolution
The description states that Mastery aims to separate recognizing a concept from being able to explain its mechanism, and does so while the text remains open in front of the user.
It evolved from an initial idea of a branching reader into a system focused on transfer checks and teach-backs. This pivot was driven by time constraints but also reflects a stated conviction that studying without checking oneself leaves little behind.
The authors claim that:
- Answering questions helps, but formulating ideas in your own words is what makes them stick.
- The teach-back is the heart of the product, not a bonus feature.
- The evaluator refuses to accept fluent paraphrasing — it requires mechanism-level evidence.
Inference The positioning centers on active learning and retention through structured feedback, rather than passive consumption or note-taking.
Target Customer & ICP
The description does not explicitly state who the target customer is. However, based on the use case:
- Users import texts (e.g., books, articles)
- They are interested in deep understanding, not just skimming
- The app supports exporting to Obsidian, suggesting a user base that values structured knowledge management
Inference The ICP likely includes students, researchers, or professionals who want to deeply understand and retain information from texts. It is not described as targeting casual readers or general note-takers.
Business Model & Pricing Evidence
There is no evidence in the description of a business model or pricing strategy. The project is presented as a hackathon submission with no mention of monetization, subscriptions, or sales.
Inference No commercial structure is evident from the self-reported description.
Technical & Delivery Signals
The product is built using:
- OpenAI GPT models (specifically gpt-5.6-luna)
- Codex for implementation and testing
- React, TypeScript, Vite, PostgreSQL, Supabase
- The system streams responses, maps concepts, generates checks, and evaluates teach-backs
Key technical elements:
- All structured output is validated server-side
- Codex verified GPT guidance, scaffolded the app, and implemented core flows (state model, streaming route, PDF import/export)
- Tests are run end-to-end after every change
Inference The system is built with a focus on AI integration, structured outputs, and automated testing. It appears to be a prototype or MVP, not a production-ready product.
Traction & Maturity Signals
There is no evidence of traction, revenue, customers, or adoption beyond the self-reported project description. The authors note that it was built during a hackathon and that they had limited time, with sessions ending in working prototypes.
The project has:
- A team of two members
- No mention of users, usage metrics, or product-market fit
Inference There is no evidence of traction or maturity beyond the initial prototype stage.
Competitive Context
The description does not provide any information about competitors. It does not reference existing tools in the learning or knowledge management space, nor does it explain how Mastery compares to them.
Inference No competitive positioning or market analysis is evident from the self-reported description.
Key Risks & Red Flags
- No traction or revenue evidence: The project is described as a hackathon submission with no commercial data.
- Unverified claims: All descriptions are self-reported and unverified.
- Limited team size: Only two members, which may limit execution speed or depth.
- No pricing or monetization model: No indication of how the product would be sold or funded.
- Unclear scalability: The use of a single AI model (gpt-5.6-luna) and Codex for implementation suggests a prototype-level system.
Diligence Questions To Ask The Founders
- What is your plan to validate the learning effectiveness of the teach-back mechanism?
- How do you intend to scale beyond the current prototype, especially with AI model limitations?
- Are there any early users or test subjects who have tried the system?
- What is the long-term vision for monetization or product-market fit?
- How does Mastery differentiate from existing tools like Anki, Obsidian, or Notion in terms of learning outcomes?
Investment/Partnership Verdict
Not evidenced.
The description provides no data on revenue, customers, traction, or commercial viability. It is a self-reported hackathon project with no indication of product-market fit, monetization, or scalability.
Confidence: Low.
This analysis is based entirely on the authors' own account — unverified and self-reported. No external validation, usage metrics, or financials are available. The project appears to be in an early prototype stage, and there is no evidence of commercial traction or a clear business model.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.
The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.

