The Standards Engine

The code on the page may not exist — and the model cannot tell you that

A ministry official can open any general-purpose AI system today, ask for a Grade 7 science lesson on the water cycle aligned to the national curriculum, and receive something usable in about nine seconds. It will have a warm-up, timed phases, differentiation, and a plenary. Near the bottom, it will name the curriculum objective it claims to address — a code, formatted correctly, sitting confidently on the page.

That code may not exist.

This is not a defect that better models will retire. It is structural. A language model is trained to produce plausible text, and a curriculum code is text. A model that has never been shown Qatar's national science framework can still produce a string shaped like a Qatari objective code, because the shape is learnable from context while the content is not. The model is not lying. It has no concept of the difference between a code it has seen and a code it has inferred. Confidence is not calibrated to provenance — it is a property of the prose style.

For a teacher, the consequence is an invisible tax. Every reference must be checked, and checking is the part that takes the time the tool was supposed to save. You can run that check today: our free code checker looks up the codes in a lesson you already have, against the Common Core, England's national curriculum and CBSE. For a ministry, the consequence is more serious: the audit trail breaks. An authority's core question about any classroom is not what did the AI write? It is what was taught, and did it match what was required? Once AI-generated material circulates with fabricated curriculum references, that question becomes unanswerable in principle.

Authorities across the Gulf are not hesitating because they doubt AI can produce teaching material. They are hesitating because they cannot certify what it produces against their own standards, and an authority cannot endorse at national scale what it cannot audit.

The gap between AI-generated material and curriculum-compliant teaching is not a gap in quality. It is a gap in evidence. That gap is what this paper is about.

(Verified) or (Indicative) — never disguised

EdSmartly's answer is not a better prompt or a larger model. It is a distinction, applied without exception, at the point where the claim is made.

Every output ends with a "Curriculum objectives covered" section. It is not optional and not an afterthought — it is a required part of every generated document: lesson plan, assessment, report, Socratic ladder, practice dialogue, weekly module.

Within that section, every objective carries one of two labels:

The second half of that rule matters more than the first. It would be trivial to label everything (Verified) and move on. The discipline is in refusing to let an unverified proposal dress itself in the visual authority of a national code — because that dressing is precisely what makes the trust deficit invisible.

We are aware this makes our unconfigured product look weaker than a competitor's. A school that has not had its own framework loaded sees (Indicative) labels where a rival shows confident codes. We accept that trade. The alternative is to be indistinguishable from the problem.

One framework flips every output from Indicative to Verified

The (Indicative) label is not a permanent condition. It is a prompt. A school shares its scheme of work and EdSmartly loads it as that school's private curriculum framework. From that moment, every future output for that school flips from (Indicative) to (Verified) — carrying the school's codes, in the school's wording, in the school's sequence.

There is no integration project. No data-sharing agreement. No engineering engagement, no professional-services line item, no six-week onboarding. A head of curriculum sends the scheme of work they already maintain to support@, and EdSmartly loads it. The school then sets its default curriculum and, if it wants, edits objectives — disable, reword, or add — directly in Settings.

Two properties that make this more than a convenience

First: the school's framework outranks the global bank — automatically. EdSmartly ships with a global objectives bank that already holds the official objectives of the Common Core, England's national curriculum and CBSE, for the grades and subjects loaded so far. When a school's own objectives exist for a given subject and grade, they are the ones cited, always. The precedence rule is not a setting an administrator might forget to enable; it is how the system resolves objectives.

Second: the framework is the school's alone. A school's loaded curriculum is structurally invisible to every other school on the platform — enforced at the database layer, not by application logic that a bug could bypass. A school group's bespoke framework is intellectual property, and loading it onto a shared platform is only rational if isolation is architectural.

What this buys the classroom

When outputs cite the school's real objectives, the lesson plan stops being a document the teacher must reconcile with the scheme of work, and becomes a document already expressed in its terms. The head of department reviewing it is reading their own codes. The inspector asking "which standard does this address?" gets an answer that resolves. And once outputs carry real codes, coverage becomes measurable. Not "how many lessons were generated" — a usage metric. Rather: which standards have actually been taught, and which have been missed.

What we will show you — and why it is not here yet

EdSmartly is early, and has no outcome data to publish yet. A paper arguing that unverifiable claims are the problem cannot illustrate itself with unverifiable claims. We would rather show three real exhibits from one school than synthetic charts from an imagined hundred.

Once founding schools are using the platform, this evidence will be available on request, with the school's permission and with identifying detail removed. Below is precisely what we will put in front of you, so that you know what to ask for and can hold the request to it.

Three mechanisms, each inspectable

1. Isolation: each school's framework is invisible to every other

Curriculum objectives carry a tenant identity. Row-level security in the database determines visibility: a request from School A can read the global bank plus School A's own objectives, and cannot express a query that returns School B's — not because the application declines to ask, but because the database will not return the rows. Application-layer permission checks fail open when a developer forgets one. Row-level security fails closed: a new feature inherits the boundary automatically.

The same mechanism governs teaching history, school settings, libraries, and Student Practice sessions. A network director sees aggregates across campuses and nothing else — adoption and activity numbers, never a campus's settings, library, or teacher history. That is not a policy we promise. It is a boundary the schema enforces.

2. Grounding: the model is given the objectives, not asked for them

At generation time, EdSmartly retrieves the objectives that apply to the selected curriculum, grade, and subject — the school's own if they exist, the global bank otherwise — and injects them into the prompt. The model is not invited to recall what a Qatari Grade 7 science objective looks like. It is handed the objectives and instructed to work from them, to cite them, and to distinguish what it was given from what it inferred.

The same discipline applies to resources. Lesson plans may cite only from the school's approved resource catalogue. The model is prohibited from inventing a URL. It cites what the school has vetted, or it cites nothing.

This is why the (Verified)/(Indicative) distinction is trustworthy rather than decorative. It is not the model self-reporting its confidence — a notoriously unreliable signal. It reflects where the text came from: objectives supplied by the school are (Verified) because the system knows it supplied them.

Every generation is a record. Every commitment is published.

3. Audit substrate

Each generation is written to an immutable record carrying the prompt version, AI provider and model, token counts, latency, and — critically — the objective codes the generation was grounded in. That last field is what makes ministry-tier reporting possible. Coverage analytics are not reconstructed later by parsing prose for curriculum references. They are read from a column that was written at the moment of generation, from the objectives the system itself supplied.

Student Practice extends the same substrate. Every session records the teacher, school, curriculum context, and summary; each student response stores the AI's diagnosis and a misconception label. That label, aggregated across sessions and grouped by objective, is the heat-map — derived from real diagnostic data, not from teacher self-report.

The governance posture

Student Practice is teacher-mediated: the teacher runs the dialogue on their own account, with the student beside them. There are no student accounts. There is no student email address, and no persistent student record. Sessions are scoped by row-level security to the teacher who ran them; administrators see aggregates only.

This is published, not merely practised. Every category — the student's first name, the response text, the AI's diagnosis, the misconception label — is disclosed in EdSmartly's privacy notice (version 2026-07-17, in English and Arabic), together with the retention period and the rule that administrators see aggregate misconception statistics and cannot read an individual student's responses.

Instrumenting curriculum implementation — not buying a content generator

An authority that deploys EdSmartly across its schools is not buying a content generator with a compliance wrapper. It is instrumenting curriculum implementation.

Consider what becomes visible when every school in a system generates teaching material against its own framework, and every generation records the objectives it addressed:

• Per-standard coverage, system-wide. Which objectives are being taught, in which schools, at what point in the term — observed continuously, as a by-product of the work teachers were doing anyway.
• Per-school adoption. Which schools have uploaded their framework at all. That single metric is a sharper signal of curriculum seriousness than most inspection instruments produce.
• Misconception patterns, aggregated by subject and grade. Where students consistently misunderstand the same standard across many schools, that is not a school-quality finding — it is a curriculum-design or teacher-development finding, and precisely the class of insight a ministry exists to act on.

The contrast with inspection is not that inspection is unrigorous. It is that inspection is a sample, taken at an interval, in the presence of the inspector. The data described above is continuous, unannounced, and generated by the teaching itself.

Small enough to shape; serious enough to trust

EdSmartly is a small platform. A ministry adopting a large incumbent inherits a roadmap set elsewhere for a market with different standards. A ministry adopting EdSmartly at this stage can shape what curriculum governance means in the product — because the architecture is settled and the surface is not. The isolation model, the audit substrate, and the (Verified)/(Indicative) discipline are already load-bearing and will not be traded away.

What we build next

Every item below is not yet built. It is listed to show direction and, equally, to mark the boundary of what is demonstrable today.

• Curriculum ingestion engine. Today a school sends its scheme of work and EdSmartly loads it. Next, EdSmartly parses the curriculum documents an authority already publishes — PDF and XML — and constructs the framework automatically. This turns (Verified) from a school-by-school action into a system-wide default.
• Student self-service practice with personal accounts. Practice dialogues that a student runs independently, with the teacher receiving the diagnosis. This crosses a governance line — it would introduce student accounts — and will not ship before the data-protection framework for it is published, reviewed, and agreed with the schools concerned.
• Competency mapping. Relating objectives to one another — prerequisites, dependencies, progressions — so that a misconception at Grade 7 can be traced to the Grade 5 standard it depends on.
• National standards graph. A queryable representation of a national curriculum, its progressions, and observed implementation across every school using it.

Contact

hello@edsmartly.com · EdSmartly.com · app.edsmartly.com
EdSmartly is a service of Axiom Intelligence Partners LLC.
This document may be shared freely in unmodified form.