A parent types what they want their kid to understand. Kindling builds a program
for that one specific child, runs it as a conversation, and reports back with questions to ask
at dinner.
Prototype
What it looks like right now
Three screens from the working prototype. Names and details are stand-ins.
The parent writes the curriculumType a subject in your own
words. A five-lesson arc comes back, editable and reorderable. Nothing reaches the child
until you approve it.The child argues with itOne idea per exchange. The options are
directions of thought, not an answer with three decoys, and the child can always answer in
their own words.The parent gets it backNot a score. What the child pushed back
on, what they said unprompted, and three questions to ask at dinner.
Scope
What was deliberately left out
StreaksSpeed scoringChild accountsStored audioIn-app rewardsRewinding a finished checkpoint
Each one was cut, not forgotten. Streaks aim guilt at a
child. Scoring speed corrupts the only real signal, because a kid who learns time is measured
starts tapping to finish.
Open problem
What isn’t solved yet
Kids are fast at gaming UI patterns. If a child can pick the right answer without understanding the idea, the system isn’t ready. Making fake comprehension impossible is the open problem.
Open to build with
Curriculum designChild developmentLearning scienceTeaching, any agePrompt and eval designiOS
Roles are not posted. Work out what is missing and pitch it.