Kartora

A new way of learning for children: a map of what can be known, lighting up as a child comes to understand it.

Alignment draft, 7 November 2026. Working name was MDL. This records a brainstorm, so it is a starting point and will change. For the architecture, the Blueprint wins where the two differ. The Prototype Plan holds the next steps.

Agreed settled in discussion Proposed raised, not decided Open still to answer

Why, vision, mission

First draft Proposed

Why
Every child can understand, but school gives them all the same path at the same pace and rarely checks that they did.
Vision
Every child grows up holding a living map of what they understand, theirs for life.
Mission
Give every child a patient tutor that meets them where they are, never lies, and answers to their family.
Line
Learning is an infinite game.

The problem

School has kept one shape for 100 years: manual, narration, homework, test, then the same again next year with more on top. Knowledge flows one way and the child has little say. Technology changed the medium, chalk to PowerPoint, and left the method alone. Many teachers are weak, and phones now compete for every child's attention.

School also won't change quickly, and children still have to pass it. So Kartora starts beside school and helps with it, then takes on more over time.

The model in five ideas Agreed

IdeaWhat it is
GraphDisciplines and chapters, each with its content, how it's measured, and its relations. The same for everyone, and public as Kartora's catalogue.
LensThe education country: the language and notation, the mother tongue and foreign languages, typical ages and what comes first. Age is only a reference. Neither changes the content.
TemplateA kind of step: a story, an explorable, an exercise, a check, a quest. Every template has three parts: Kartora's knowledge and measure, the parent's knobs and allowed bias, and the child's shape and design. It carries its own harness for the AI.
SessionA path across a few chapters, made of templates the AI fills for one child, seen through the child's lens.
ProfileOne colour per chapter per child, from the evidence of each session.
Numbers Division Multiplication Fractions Ratios Percentages Map scale Probability

An invented example of one child's map. Faded means new, full colour means close to 100% assimilated. The dashed link crosses into Geography.

The graph

The graph is the core of Kartora. It is a pure knowledge base kept by Kartora's supervisors. It says what is true and how things relate, and nothing about how to teach them, who is learning, or which school or country they are in. Agreed

LevelDecidesChanges
1. DisciplinesWhich disciplines existVery rarely
2. ChunkingHow each discipline is cut into chapters, roughly 100–200 eachRarely
3. ChapterIts content, what enters and what leaves, and its relations to other chaptersRegularly

Example chapter Proposed

Comparing fractions (Math, M-042). Begins at unit fractions of one whole, ends at comparing any two fractions.

Points: same bottom number, compare the tops (comparison); same top number, the smaller bottom is bigger (comparison); different both, rewrite with a common bottom number (procedure). Misconception: a bigger bottom number means a bigger fraction. Measured by 12 check questions.

Requires parts of a whole (strong) and multiplication. Leads to adding fractions and ratios. Related to map scale (Geography) and concentrations (Chemistry).

A good chapter Proposed

Disputed content Agreed

Where facts are truly disputed, a node holds variants, each saying whose position it is. A default can come from the country, and parents or teachers can adjust it. The session is honest that the point is disputed.

The lens Agreed

Templates and sessions Agreed

Knowledge and method are two different things. The knowledge sits at Kartora, in the graph. The method is how it reaches one child: templates, filled by the AI with what that child likes. That's what keeps a child interested, so it's as fundamental as the graph.

A template is a kind of step. Some present a topic: a story, a comic, an explorable picture, a timeline. Some are exercises: choose, fill the word, build, sort, order, spot the mistake, teach back. Kartora's check measures. A quest takes it away from the screen. Kartora ships them, versioned with its releases, and each release adds more and better ones.

Every template has three parts, always:

PartWhoseWhat it holds
Knowledge and measureKartoraThe chapter's points it carries, the misconception it tests, and how it measures: nothing, practice, or Kartora's check
Knobs and allowed biasParentThe lens, depth, how strongly interests flavour it, themes to avoid, which disputed view comes first
Shape and designChildThe world it's told in, characters and their names, colours, pictures, how the child likes to start

Each template also carries its harness: the rules the AI follows when it fills it, and what plain code checks afterwards. Every claim comes from the chapter's points; a wrong answer is a listed misconception; numbers are computed by code; the check's words are never changed. So the AI prepares the session, the parent decides only what is learned and approves, and the template holds the rest.

The check is the same for every child. Only the line before it can belong to the story. That keeps colours comparable across children, families and countries.

A session starts in one of two ways: the AI proposes it from the child's map, or the child asks, for example with a worksheet from school. The material is always mapped onto the graph first. A typical session: a story to present, two or three exercises with branches for likely mistakes, Kartora's check, a teach back, a quest.

The child decides how, never what: their interests, colours and names shape every template, and they can start sessions. What is learned is set by the graph and the supervising adults. The child's part never leaves the family.

The profile

People and who has a say

WhoRole
ChildLearns, starts sessions, owns the shape and design part of every template
ParentTakes the teacher's place at first: sets the education country and subjects, opens chapters, sets knobs and allowed bias, approves sessions, sees the dashboard
TeacherComes later, if schools adopt it, and sees their classes
SupervisorsOwn the graph, the lenses and the catalogue, and their releases
Researchers and specialistsInvent and improve templates and evaluation over time
AI modelsPrepare sessions by filling templates inside their harness. They can be swapped as better ones appear.

Knobs and hard rules Agreed

Behaviour is adjusted by knobs, each with an owner. The parent's knobs are the allowed bias every template reads: the education country, how deep to go, how much interests flavour a session, themes to avoid, which disputed view comes first, time in a day. New ideas can become new knobs without touching the data model.

The hard rule: Kartora never teaches a lie, whoever asks. Knobs change emphasis and coverage, and they stop at the truth.

Built to grow Agreed

An upgrade must not force a change of the data model. Each part changes alone and meets the others at a few stable points.

PartWho has a sayHow it changes
GraphSupervisors, subject researchersReleases
Templates and evaluationPsychologists, pedagogues, computer scientistsNew and better templates in each release
AI modelsWhoever builds the best onesSwapped
Limits for this childParent, later the teacherSet in the profile

Stable points Proposed: chapter IDs and releases, one template contract with its three parts, evidence records, colour derived from evidence, and the AI model behind one seam.

Think of it as reinforcement learning for humans: an inner loop per child, and an outer loop where experts learn what works across children. Two warnings come with that: anything optimised against a metric learns to game it, and a child has only one childhood to experiment on.

On Nervur Agreed

Kartora is a use case of Nervur, and the two go in parallel, so it is designed as if Nervur is finished. Nervur handles the relations between children, parents, teachers and researchers, and the devices they use. The data model doesn't depend on any device. Children will probably use an app. A game can be an organ, and how organs reach a general app is Nervur's question.

It uses public Nervur alone. Every faculty and organ it needs is developed inside Kartora, with nothing from Bookarest Digital.

Two stages. First it's an emulated SaaS: people register an account at kartora.org, signing in by OAuth, and Kartora keeps those accounts on Nervur as a keeper. Later, as Nervur grows, it also offers real Nervur accounts.

Privacy is why Nervur was chosen. Families can hold their own organisms. Kartora's organisms hold the graph and scoring alone, with no children's names or accounts. The emulated SaaS is only a transition. Agreed

Each side keeps its own half. The family's organisms hold the child's name, preferences, uploads, session text, evidence and scores. Kartora's hold the graph. Proposed

Keep how someone signed in separate from everything else, so the second stage is a swap and not a rebuild. Proposed

Kartora may receive metadata, never names or details of a child, so researchers can work and the system can be evaluated. Teachers can receive their own kind of information. Faculties on the family's side filter what leaves, and evaluation may be done by Kartora on metadata. Agreed

How that could work Proposed: one outgoing filter on the family's side, with a separate relation and view for each receiver. Only fixed fields leave, such as chapter, check question, right or wrong, time band and method version. Free text never leaves. The parent can read exactly what left. Kartora keeps the check answers, scores the metadata and returns the colour.

What Nervur brings. SaaS can connect teachers, parents and researchers too. Nervur keeps the privacy and the boundaries of what each one may see, and puts control of the relations in the family's hands. In a SaaS those boundaries are a vendor's promise. Here they're the structure, and no party holds the whole child. Agreed

Bring your own AI Agreed

Sessions run in the family's organism, driven by the family's AI. The parent chooses the model and decides how much data that provider sees. Kartora doesn't own session data, and may offer its own trained models for some parts later.

The shape Agreed:

Sessions are prepared first Agreed: the parent's AI authors each session ahead of time, with its explanations, questions and branches for likely mistakes, and writes it into the child's organism. The browser plays it with no model live, plain code scores what it can, and the AI reviews the results at its next run. The child can also open sessions, within what was pre-approved.

How that could work Proposed: a shelf of ready sessions the child picks from; requests and uploads that wait for the AI's next run; and an approval knob, from approving each session to automatic within opened chapters.

The family also needs models it controls that can run with no parent at the keyboard, such as OpenRouter or hosted models on the parent's account, or claude -p authorised in the family organism. Agreed

Connecting the dots Proposed: four organisms and one seam.

OrganismHolds
KartoraThe graph, lenses and templates, their releases, the catalogue and the faculties
Parent (local)The parent's own organism: the anchor, MCP to their AI, the edge pilot, claude -p and local models
Family (edge)Always on, in the parent's own Cloudflare account, as a keeper: knobs, approvals, budget, the child's map, hosted authors
Child (browser)The shelf, the player and what the child does

Parents have organisms locally, and use an edge as a keeper. They control the Cloudflare account from the local organism, with the edge pilot. Agreed

The seam is the author: anything that can turn a request into a session. It may be the parent's AI by MCP, a hosted model, claude -p or a local model, and the family's knobs choose which. The child's organism never knows which one wrote a session. A request flows from child to family, to an author, through approval, and back to the shelf.

Still to settle Open: how a child can be present at an organism the parent controls, how simple the edge setup can be for a non-technical parent, whether live sessions come later, and which models are good enough.

How the model maps onto Nervur hasn't been designed yet.

The MVP

There is no finish line and no "success": it's an infinite game of updating the profile against the graph. Agreed The first children should still teach us three things: Proposed

PartStarting pointStatus
ChildrenAges 9–12 for the first test only. The product isn't tied to an age range, since age is only a reference.Agreed
DisciplinesEasy ones with no bias, math first. Mother tongue is also a candidate.Open
GraphOne slice of math, starting down at numbers and basic operationsProposed
TemplatesAbout 5: story, choose, build, Kartora's check, teach backProposed
SessionsProposed by the AI, or started from a PDFProposed
PeopleParent and child onlyAgreed
DashboardThe coloured map and sessions doneProposed

Ideas on the table Proposed

All of these interested you. None is decided. Most of them become templates.

Method

Motivation

Risks to design for

What Nervur makes possible

Testing cheaply

Try the method by hand for two weeks with 5–10 children, a small paper graph, and a parent running sessions through a model.

Open questions Open

  1. Math alone first, or math and the mother tongue?
  2. Who are the first children, how many, and in which language?
  3. What does "quality of relation" hold: type, strength or both?
  4. If a chapter gains content, what happens to a child at 100%?
  5. Does evidence on one chapter affect the chapters linked to it?
  6. How much does one mistake count against each chapter it touches?
  7. Where do concepts that cross chapters go, such as the Industrial Revolution? Does each discipline have its own way of cutting chapters?
  8. Do history's chapters fit in 100–200 if the graph holds every country's history?
  9. Does the graph hold finer points inside a chapter's content, so evaluation can name what was missed?
  10. What happens to uploaded material that maps to nothing in the graph?
  11. Is the graph built by hand, or drafted by AI and approved by people?
  12. Who maintains the age reference data, and where does it live?
  13. What exactly counts as disputed, and how is a disputed point evaluated?
  14. Does a parent open whole disciplines, or single chapters too?
  15. What rules apply to children's data and to sending it to model providers?
  16. Who pays, and for what?
  17. Who curates each country's lens: typical ages, emphasis, chapter names and check questions in its language?
  18. Which countries come first?
  19. Which knowledge shapes does the graph need, and does every point get exactly one?
  20. Who invents templates, how is a new one tested before release, and which come first?
  21. How are pictures made for the child's world: a library drawn by Kartora, or generated and checked?

The company

Founded by three friends, with Europe first and the world as the goal. The country of registration isn't decided, and Estonia is the likely choice. Agreed

FounderFromRole
RazvanRomania, ItalyCTO and CPO
MichaelGermanyCFO, funding and investors
MarcusGermanySales, PR and communication

Still to answer Open: who brings learning science and child psychology, and who pays for an account and how much.

Nervur is a tech stack for Kartora, used under its Apache-2.0 licence, with no other link between the companies. Agreed

The name

Kartora is chosen. Agreed It comes from map words such as Karte, carte and kartë. You found .eu, .ai and .org free, and WHOIS confirmed kartora.org unregistered on 7 November 2026. Nothing has been registered.

A formal trademark search of the EU, WIPO and UK registers is still needed. Open The first thing to clear is CARTORI, a UK application filed in April 2026 for software, which sounds very close.