⚙️ Tesseract Engine V1

In Smallprof, an answer is not just a result. It is a trace of learning. Tesseract Engine V1 progressively links these traces to build a dynamic picture of the child's journey:

Answer → Skill → Memory → Adaptation → New experience

The engine can therefore take the child's progress into account instead of treating each exercise as an isolated interaction.

🧭 Why did we create Tesseract Engine?

A child does not learn by answering a string of independent questions. Each experience is part of a progression.

A success can confirm a skill. A mistake can reveal a difficulty. A series of experiences can point to something worth revisiting.

Tesseract Engine was designed to give the game the memory it needs to link these traces together.

The goal is not to make the game more complex.
The goal is to make its journey more coherent.

🎮 A game that remembers

In many educational games, each exercise can be treated as a fresh interaction:

Question → Answer → Reward → Next question

Tesseract Engine takes a different approach. Each answer can enrich the child's history. The system can notably keep information related to:

• the skills being worked on
• previous answers
• successes and mistakes
• the types of mistakes made
• progress
• skill memory

Seen as a loop, this can look like:

Answer → Trace → Skill → Memory → Adaptation → New experience

The goal is simple: not to treat each question as an isolated event.

🧠 From answer to skill

A correct answer does not simply mean “+1”. It can provide information about a skill being worked on.

Likewise, a mistake is not only a wrong answer. It can help identify how the child went wrong.

The engine can therefore progressively build links between:

what the child does → the skill being worked on → what the system already knows → what can come next

🔄 A memory that follows progress

Tesseract Engine relies on a skill memory. This memory lets the system keep traces of the child's journey instead of starting from scratch with every new game. It progressively builds a history of the child's journey:

What has been practised.
↓
What has been mastered.
↓
What has been difficult.
↓
What can be revisited.

The goal is not to permanently label the child. On the contrary, progress stays dynamic. A skill that looks mastered today can be revisited later. A difficulty can disappear. A new skill can emerge.

🎯 Adapting the experience, not just the difficulty

Adaptation is not simply about making questions easier or harder. The engine progressively tries to take the child's journey into account.

A new experience can be shaped by the traces left by previous ones. This makes it possible to build a progression in which exercises are not completely independent of one another. Each new experience can become the intelligent consequence of those that came before it.

🧩 Several parts, one experience

Smallprof has different families of games and skills. Tesseract Engine is designed to link these parts together. A skill practised in one laboratory can therefore become useful information for understanding the child's overall journey.

The child does not need to manage this complexity. They just play. The engine works in the background.

🌱 A progression that stays invisible to the child

The child should not have to understand a system of rules, dependencies or data. They simply see:

Game → Answer → Feedback → New experience

Behind this simplicity, the engine can progressively link the traces of their journey.

🔬 An architecture built to observe and learn

Tesseract Engine does not try to give the child an overall score. It instead tries to keep information precise enough to let the system evolve alongside their journey. The engine notably distinguishes:

✨ The Tesseract principle

The name Tesseract evokes a structure able to link several dimensions of the same object. In Smallprof, this idea is used as an architectural metaphor: an answer is not just an answer. It can be linked to several parts of the journey:

Answer
↓
Skill
↓
Memory
↓
Progress
↓
Adaptation
↓
New experience

The engine therefore tries to create useful connections between the different traces of the journey.

👨‍👩‍👧 For the child, it all stays simple

Everything that happens inside the engine is meant to stay invisible to the child. They don't need to understand the mechanics that organise their journey.

They play.
They experiment.
They get feedback.
And they carry on with their adventure.

👨‍👩‍👧‍👦 For parents

Tesseract Engine is designed to help keep a richer picture of the journey. The data can be used to show parents:

• the skills being worked on
• successes
• certain difficulties encountered
• certain types of mistakes
• how the journey has evolved

The goal is not to reduce the child to statistics. The data is used to tell their learning journey with more precision.

🔐 A progressive approach

Tesseract Engine V1 is designed to evolve progressively. We do not claim that an algorithm can, on its own, measure the quality of learning. The engine provides an adaptive infrastructure that links the game's traces. The real educational impact must then be observed in how the product is actually used, with real children.

That is why Smallprof distinguishes between:

• What the system knows.
• What the designer decides.
• What observing children can actually confirm.

🚀 Tesseract Engine V1

Tesseract Engine V1 is the first generation of this architecture. Its principle can be summed up in one sentence:

Every answer leaves a trace.
Every trace can enrich the journey.
And the journey can shape the next experience.

Smallprof thus progressively turns a series of games into a coherent learning journey.