Mojo the Examiner
reads what you upload · A student's team
Working today
The challenge
The world you are about to walk into is being rewritten faster than any prospectus can keep up with. Whole fields are being reshaped, the meaning of a qualification is shifting under everyone's feet, and nobody hands a seventeen-year-old the hundred data points they would need to choose well. Before any of that becomes your problem, though, there is a smaller and duller one in the way. You have spent years building something real — transcripts, certificates, a project you stayed up too late finishing, a language you learned because you wanted to. Then you go to apply, and none of it is a form. It is a folder nobody has the time to read properly, and you have no idea which parts of it actually count for anything.
What it does about it
Now imagine you never have to explain your own history again. The Examiner exists to read it — every page of that folder, patiently, the way nobody in an admissions office ever has time to — and to turn what it finds into evidence the rest of your team can act on. You stop being the person defending a pile of documents, and start being someone whose record simply speaks.
How it works
It reads the documents you actually have — a transcript, a diploma, an English certificate, a CV — and pulls out the specific things inside them: which subjects you took and at what grade, which test you sat and what you scored, where you have worked, in what role, and for how long. Every one of those is shown back to you as something you can correct, so nothing enters your file that a page is not standing behind.
What you get
Your own record, in a shape the world can finally read — every claim traceable to a page you can point at, instead of a form you filled in and hoped was enough. And what it establishes does not stay with it: the Analyst checks your eligibility against it, the Cartographer measures your skills from it, and the Narrator writes from it.
The machinery
- Producesstudent_document_analyses
- Can act whenapp/api/docs/analyze (consent checked there, not here)
Read from the same manifest the product runs on, so this cannot describe machinery that does not exist.