Schools · 2027
The same engine, pitched at the reading age it is talking to.
An explanation written for the average eleven-year-old is written for nobody. The engine that already rewrites an undergraduate explanation until it fits can pitch to a reading age instead of to a year group: that is a configuration of the same system, not a different product.
Nothing described on this page is built. It is a 2027 line on a roadmap, and a school that plans around it before then is planning around nothing.
- 2027planned, not promised
- 0lines written
- 1engine it will run on
Why it is not a second product
One engine. Very different rooms.
Everything Corvexal builds requests a capability and lets one configuration file decide which model fills it. A school surface is a different set of constraints on the same orchestration layer, the same memory and the same design system, which is why adding one is a configuration rather than a rebuild, and why it can be free the way EMBER is free.
A school is not a university with smaller chairs.
Decided
Settled
It is the same engine
No separate codebase, no separate model, no separate price.
It is free to the student
The same permanent free tier. No bill, no account to start.
Reading age, not year group
The unit of adaptation is what a person can currently read.
Not decided
Still open
Safeguarding and data posture
What a district needs to sign is not written down yet.
Who administers it
Teacher, department or district, and it changes the product.
One surface or two
The brand architecture splits K–8 from 9–12. The software may not.
What we will not do
We will not put a child behind an account wall to measure them, and we will not sell what a child got wrong to anybody, ever: not as analytics, not as research, not anonymised.
If this is your problem
Tell us before it is built, not after.
If you run a school, a district or a ministry and this is the problem you have, the useful time to tell us is now, while the constraints are still being written down.