Resolve before generating
Ambiguous topics should be confirmed before credits are spent. A confident lesson on the wrong meaning is still a failure.
Built for what happens after the answer
Nodebook began with a simple frustration: getting an explanation is easier than ever, but keeping the understanding is still hard. The product is designed around the full path from curiosity to later recall.
The product belief
An AI answer can be useful, clear, and still disappear from memory. Nodebook treats the explanation as the beginning of learning, not the finish line.
The app turns a topic into a structured lesson, makes its important concepts retrievable, and returns only the ideas that need attention. The memory system should be effective without making the product feel like a dashboard of anxiety.
Principles we build by
Show the grounding
Citations let learners inspect the material behind a lesson instead of accepting fluent text on trust.
Effort at the right moment
Recall is useful, but constant testing is exhausting. Retrieval should appear where it helps.
Stable means quiet
When nothing needs review, the product should say less. Detailed memory data belongs in Brain.
One knowledge state
Reading, flashcards, Recall Lock, and Audio Recall should strengthen the same concepts rather than create separate silos.
Honest cost
If an audiobook is cached, replaying it should not look like a fresh paid generation.
How AI is used
AI helps resolve intent, gather and synthesise source material, structure lessons, create appropriate practice, and generate narration. It can still make mistakes. Nodebook uses source grounding, validation, user correction, and clear limits to reduce those errors rather than implying they are impossible.
Privacy and audio
Private lesson access is tied to your account. Audiobook files are delivered with short-lived signed links. Identical narration may be retained as a shared anonymous cache so another learner does not pay to generate the same audio again. Account deletion severs the link between that cache and the person who requested it.
The full current details are in the privacy policy. Product and privacy language should describe the system that exists, not the one we hope to build later.
Where Nodebook is going
The long-term goal is not to become another general chatbot. It is to become the place where anything worth learning can become a clear lesson, a calm audio experience, and a durable part of your personal knowledge.