How Ebiblo runs on Emidox

Ebiblo is a knowledge-check app: a tutor uploads material, question sets appear, a person approves them, learners answer on a phone and see why each answer was marked as it was. It is a separate product with its own customers. It also contains no AI of its own. Every question it has ever shown a learner came out of an Emidox agent.

Here is the flow, node by node. The source is an Ebiblo input page — an Emidox input dataset that a tutor opens from inside Ebiblo. They upload a worksheet, type or speak one line about what to ask, and press Send. The first agent reads it against a long instruction: check the maths, rewrite for a Year 8 reading level, fill in missing options, produce the answer key with a worked line for each. Its output is Ebiblo's quiz page — the questions arrive there as a draft, and Ebiblo notifies the tutor.

Behind that first agent sits a second one with router mode on. When a centre runs several subjects through one form, the router reads each submission and sends it to the maths agent, the science agent or the reading agent — each with its own prompt and its own quiz page. That is the whole pipeline: one input page, a router, a few specialists, a few quiz pages. It runs on update, so it fires every time material arrives and never otherwise.

Two things follow. Ebiblo's people never open Emidox unless they want to change a prompt; the agents were made once and the two apps share a login, so the tutor stays in Ebiblo. And the same shape — an input page in, a specialist agent, a product page out — is not specific to quizzes. It is what any app built on Emidox looks like. Ebiblo just happens to be the first.