Syllabus coverage auditor
About this agent
A syllabus is loaded once as the yardstick — topics, weeks expected, and the share of board marks each topic carries. Against it sits the teaching record: what was covered, in which week, and for how long. The audit reports three states rather than two — covered, covered in name only, and not touched — because twenty-five minutes on a topic worth twelve marks is the failure a tick-box tracker misses entirely. Gaps are ordered by marks at risk, not alphabetically, and the same gaps read as more urgent late in the term than early, because they are.
What changed with Zenmem?
The same agent, built twice against the same contract — once on Zenmem, once on MongoDB + LangChain/LangGraph.
Before → after
Before With Zenmem
What the team gained
- The classroom agent writes the teaching record into the same store the audit reads, so a live deployment imports nothing and nobody enters a topic twice.
- The department view is the same syllabus read across sections — a filter, not a second aggregate table kept in step by a nightly job.
- Marks weights sit on the syllabus record itself, so ordering gaps by marks at risk needs no join.
- Three coverage states rather than two costs a comparison, not a schema column and a migration.
- A class with no teaching record reads as covering nothing without any special-casing, because an empty scope is simply empty.
How memory is scoped
Long-term memory, filtered to one class. The syllabus and the teaching record live in the same store, which is what makes the audit a lookup rather than an import: in a live deployment the classroom agent has already written the teaching record there, so nothing has to be entered twice. The department view is the same syllabus read across every section.
How it works
The run order the collection walks through.
Load the yardstick
Topics with the weeks they need and the marks they carry. Without weights, an uncovered heavy topic looks the same as an uncovered light one.
Collect the record
In a live deployment this arrives from the classroom agent rather than being typed in.
Audit the gap
Three states, ordered by marks at risk. A thin pass is named as one instead of counting as covered.
Watch the clock
Same gaps, less term left — the urgency rises even when nothing else has changed.
API surface
The whole agent, endpoint by endpoint.
Endpoints
- POST /api/syllabus — load the syllabus: topics, weeks expected, and the marks weight of each.
- GET /api/syllabus/{syllabusId} — read the syllabus back.
- POST /api/taught — record a topic as taught: class, topic, week, minutes, detail.
- GET /api/taught/{classId} — the teaching record for one class.
- POST /api/audit — covered, covered in name only, or not touched — ordered by marks at risk for the current week.
- GET /api/department/{syllabusId} — the same syllabus across every section, for the head of department.