Kartora Prototype Plan

What Nervur gives us, what's missing, the order of the work, and everything a new session needs to carry on.

7 November 2026, against Nervur 0.30.49, from reading its spec, code and READMEs. Nothing was run for this and nothing is built. The order below is a proposal.

Pick up here

Read in this order: this plan, then kartora-blueprint.html for the architecture, then kartora-alignment.html for the idea and the model. Where they differ, the Blueprint wins on architecture.

Where we stopped: the idea, the model and the architecture are aligned. Nothing is registered or built. We were about to start preparing the prototype.

Next steps: decide the open questions below, then write the Nervur statements, chunk the first math slice with its points and checks, and write the first five templates.

How this workspace runs: a session in repos/ is the orchestrator. Authoring happens in a session opened in the repo itself, commits go through the repo lobe, and Nervur's changes are handed to its authoring agent as one statement each: the fault, its source, the fix and its tests. kartora-docs/ is a plain folder, not versioned, and should move into the kartora repo once it exists.

The verdict

Nervur has almost everything a prototype needs. Nothing blocks starting with the family organism on a small server and the child in a browser. The bulk of the work is Kartora's own code.

The two biggest unknowns aren't missing features. They're whether a browser home on a real site feels good to a 10-year-old, and whether the design work is bigger than it looks. Test those first.

What Nervur gives us

Need	Status	Notes
Family organism on a server or desktop	Built	Node installer
Child's organism in a browser	Built	`@nervur-org/installer-browser`
Invitations, links, standings, one-time references	Built	QUO-6, CASE-2. QUO-6 also lets a family ask for an invitation for another organism of its own.
Parent's AI by MCP	Built	`nervur mcp` reaches far organisms too. It runs on a desktop or server.
Lobes, cells, letters, alarms, jobs	Built	Core
Faculties, repo lobes, gates, releases	Built
Pages drawn from a far lobe, a website's app view	Built	The window, LOOK-5
Designs and websites at the edge	Built	`quo.systems` has a website
Calling a hosted model	Pattern works	A skin of `network` answers `{job}` and moves by scheduler rings, within the 10-second longest timeout. `openrouter` shows it, but it's private, so Kartora writes its own.
Family organism on an edge	Prove it	Cargo built and tested, no numbers measured (HOST-28). 48 MiB engine, 5-second budget.
Browser home inside a real site	Prove it	Built with tests. I found no site in this workspace embedding it yet.
Hosted model running on an edge	Prove it	Pattern proven on Node only
Edge pilot	Missing	Faculty and Node half unbuilt (HOST-7, HOST-26). Use a server, or lay an edge by hand.
File from the screen	Missing, no rule	Inputs in `genome/package/src/standard/tree/allow.ts` hold no file type. For now the parent's AI reads the PDF and sends the request.
Taking new versions by a rule	To confirm	LIB-8 mentions it. Move versions by hand at first.
Games as organs in a browser	Proposal	HOST-24. Templates are screen data drawn from the player's blocks. A lobe sends the screen data, never code (SCREEN-2).
Push, phone app, remote MCP, public log of browser code	Proposals	HOST-4, HOST-20, HOST-21, HOST-24, HOST-25, LINE-4, LINE-5, WEB-7, WEB-8. None blocks the prototype.

Found by the mock-ups

The first mock-ups are in kartora-mockups.html. They show a Romanian family living in Germany. Ana, 9, follows the German school system and keeps Romanian as a heritage language; Matei, 12, follows the Romanian one. They share one subscription, AI and home. Each child has their own map across ten subjects, a shelf, knobs, an education country and an invitation. Every step of a session is a template with three parts, and Kartora's catalogue shows every chapter and template in public. Making them raised these problems the documents hadn't caught:

The parent's screen has no relation. R1 and R2 are parent organisms owning the edge, but a parent on a phone at kartora.org is a browser. It needs its own relation, probably a browser organism made an owner by R2. Open in the Blueprint.
Family setup is the hardest step in the product. A non-technical parent can't be asked for a local install and a Cloudflare account. The first families are set up by hand, but this has to be solved before step 7.
Siblings sharing a device share one organism. An organism is one site of a browser, so two children on one tablet at kartora.org are one browser organism. It needs a player lobe per child and a "Who's here?" screen, which is no lock. To decide whether a child needs a PIN.
The outbox is per family, the colours are per child. Kartora needs a separate code per child to score them apart. One R5 relation per child would also stop it linking siblings. Open in the Blueprint.
Each country is a lens Kartora curates. The education country sets the language and mother tongue, foreign languages, typical ages and emphasis, while the graph stays the same. Each lens is real work, which paces how fast countries open. Who curates is open.
The age reference is data of its own. The atlas and the reach chart need a typical age per chapter, kept by Kartora beside the graph, and it may differ by country.
The lens is more than a language. It also sets notation (0,4 and 0.4, 12 : 4 and 12 ÷ 4), units, money and order, and in Germany the Land sets typical ages.
The check can't be themed. Its words are fixed and only translated, or colours stop meaning the same. Only the line before it belongs to the child's story.
A public catalogue changes what's paid for. The subscription pays for the service: the player and templates, prepared sessions, private checks and colours, and new releases.
The child's part is the most personal data. Interests, names and colours stay in the family and never reach the outbox.
Pictures for the child's world need a library drawn for Kartora; generated pictures come later, behind their own check.

Kartora's own work

Repo: kartora, with its gate and harness. Everything Kartora develops lives there, and nothing depends on Bookarest Digital's private repos.
Faculties, family side: family, child, player, author, graph, model, outbox, view.
Faculties, Kartora's side: graph, check, signup, studies.
Graph: the format, with points, knowledge shapes, misconceptions and checks, and the first 15–20 math chapters.
Lenses: Germany and Romania first: language, notation, units, order, typical ages.
Templates: the template format with its three parts and harness, the player's blocks, and the first five: story, choose, build, Kartora's check, teach back.
Session format, made of filled templates.
Catalogue: the public pages of chapters and templates at kartora.org.
Design: it has to draw the six screen components (frame, organism, lobe, data, app, loader), plus the coloured map and the shelf.
Website: kartora.org with the browser home, deployed.

The order of the work

Step	What	Done when	Lead
0. Prepare	Settle the decisions below. Start company, legal and trademark work. Find families and an advisor.	Name cleared, first families named, advisor found	All
1. Paper test	Two weeks, 5–10 children, a small paper graph, a parent running sessions through a model.	We know if the method engages a child	Marcus, Razvan
2. Two proofs	A browser home at a test site reaching a lobe on a server. One real template, filled with a child's interests, in front of a 10-year-old. Size the design work.	A child used it, and the design is sized	Razvan
3. Graph	Chunk the slice, answering the open chapter questions on real content.	15–20 chapters with relations, reviewed by the advisor	Razvan, advisor
4. Thin slice	One child, one session, end to end: the parent's AI writes it by MCP, it lands on the shelf, the child plays it, results reach the family, a colour changes.	The loop runs once for real	Razvan
5. Whole loop	Hosted author, fading, placement, frontier, approval knob, Kartora's relations and scoring, the outbox.	A session is proposed and scored with no parent acting	Razvan
6. First families	3–4 families set up by hand, then 5–10 children. Watch all three things we want to learn.	Several weeks of real use	Marcus, Razvan
7. Towards real families	Move family organisms to edges and measure them. Carry the Nervur gaps. Payments and signup.	A parent sets it up alone	Razvan, Michael

What we want to learn from the first children: a child comes back without being pushed, sessions and PDFs land on real chapters, and the colour matches what a parent sees and how the child does at school.

To carry to Nervur

Not yet written as statements for Nervur's authoring agent. In order of need:

A file from the screen, with a rule under DIR-58. Today LOOK-15 only carries files down to a page.
The edge pilot: the faculty and the organ's Node half.
Taking new versions by an owner's rule, if it isn't there.
How a site or an app gets its own organs, for games.
Telling a closed browser or phone, and the phone app.
Remote MCP, and a public log of browser code.

Decisions to take

Decision	Who	My suggestion
Math alone first, or with the mother tongue?	Razvan, advisor	Math alone
Who are the first children, how many, which language?	Marcus	5–10 from your own circle
Is sharing metadata optional, or a condition of use?	All, lawyer	On for the first test, by agreement
Do results go to the family after each session?	Razvan	Yes, by a letter
Who pays, how much, for exactly what?	Michael, Marcus	A family subscription for the service
Do you need OAuth, or are invitations enough?	Razvan	Parents sign in at kartora.org. Children only use invitations.
Is the family organism always an edge, or an edge or a server?	Razvan	Either. Server for the first test.
Who owns graph content?	All	The advisor or a first hire
Where is the company registered?	Michael	Estonia is likely, not checked

Graph questions still open are listed in the Alignment draft, under Open questions.

The work split

Founder	Owns	First tasks
Razvan	Architecture, Nervur gaps, data model, faculties, product	Nervur statements, first math slice, the two proofs
Michael	Company, money, legal, investors, pricing	Country comparison, lawyer, trademark, domains, cost model, provider terms
Marcus	Families, brand, story, partners, teachers	5–10 children, advisor, parent interviews, the story, a holding page

Two risks: Razvan is the bottleneck across Nervur and Kartora, and nobody owns graph content yet.

What's settled, in short

How families and Kartora relate

Kartora has its own organisms and kartora.org, and knows its customer, the parent. The family's organism is the stable ground, where the children are declared and their data is kept. A child's browser organism is a stranger until it receives the family's invitation. Example:

The Popescu family subscribes and lays its organism.
They declare Ana, aged 9. Her name and profile stay with them.
The family asks Kartora, over its standing, for an invitation for one more organism of theirs (QUO-6).
Ana opens the link at kartora.org and her browser organism accepts.
Sessions come from the family, and results go back to it.

No link: a stranger, who gets nothing.
Browser wiped or lost: the family sends a new invitation.
Ana wants her own invitation: she can't get one.
Who owns the browser organism: it doesn't matter, since everything of value comes through relations the child can't create.
Subscription ends: Kartora drops the relations. The family keeps its organism and data. It loses kartora.org and its screens, the graph, new releases and scoring. It's a car without engine or body, so the subscription stays worth paying.

The privacy promise

Kartora doesn't keep children's names, emails, addresses or other details it doesn't need. It sees what it needs to run the service, such as which chapters are asked for and how checks go. It never promises complete privacy. Metadata can sometimes identify someone, and that's accepted.

What Nervur brings is boundaries held by structure, and relations the family controls. SaaS can connect the same people, but there the boundaries are a vendor's promise.

Comparable colours (proposed)

The model never sets the colour. Fixed check questions from Kartora, generated from patterns where possible, are scored by plain code, so colours mean the same in every family whichever model it uses. Free answers are a secondary signal. Check answers stay at Kartora.

From the challenge round

Sell learning, and let privacy be the reason parents trust you. Keep Nervur out of the pitch.
Don't plan around schools early: start with families, tutors and small private schools.
Research is slower than a central platform's. Treat it like clinical trials: consenting families get a method version, and results come back.
German schools' data sovereignty concerns may be an opening. Not checked.

The name

Chosen: Kartora. You found .eu, .ai and .org free. WHOIS confirmed kartora.org unregistered on 7 November. Nothing is registered.
First risk: CARTORI, a UK application from April 2026 for software, sounds very close. Also near: T-Kartor (maps), Kartorium (software), Cartoria Ltd (skincare retail).
Backup: Lumappa, with .org and .com unregistered and no collision found.
Dropped: Orbis (domains taken, crowded), Comenia (Comenia Learning exists), Omnivia (near OMNES and Omnilya).
Spelling: voice transcription often writes Cartora. It's Kartora. cartora.org was in redemption, and cartora.com is taken.

Still to verify

These come from memory or secondary sources. Don't rely on them yet.

Provider terms: reports say Anthropic bars consumer subscription tokens in third-party products, and points to API keys, while one report suggests a change since June 2026. This matters for claude -p in a family organism. Check OpenAI and the others too.
Minors: Anthropic's consumer terms are 18+. Reports say third-party products for minors are allowed with safeguards. A parent's own use with MCP is the safe shape, since the child never touches the provider.
OpenRouter: I recall a one-click account connection for users.
GDPR: the age of digital consent runs from 13 to 16 by country. A child's learning data under an ID can still be personal data, which is allowed under the rules. Google Classroom works through the school, Duolingo-type products through parents' consent, and Kartora is the second kind. A risk assessment is probably needed.
EU AI Act: I recall AI that evaluates learning being high-risk.
Cloudflare's costs for a family edge.
The learning research behind the ideas in the Alignment draft.

How Razvan likes to work on this

Brainstorm first: align and ask before proposing, and don't be definitive on unstructured ideas.
Take the substance, not the literal words. Examples such as WhatsApp or soccer are only examples.
Think in computer-science terms: simple, abstract entities and separation of concerns.
Design with Nervur as if it's finished, then separately list what's missing.
Think in relations first. Don't invent risks that the relations already remove.
Bring ideas and challenge when asked, but stay practical. Don't over-worry about privacy or law.
It's a starting point that will grow, not a system that does everything now.
Keep the local docs and the artifacts in sync, always: every change here is republished in the same step. The README says how.
Only forward: every document, business or design, takes each decision as it's made, and holds the latest thinking alone, never its history.