Citations by default, code that actually runs, current events as raw material. A workshop you can hand to a class without lowering the ceiling for advanced students.
asks a question, drops a reading, or opens a code assignment.
routes through Research, Search, News and Code as needed.
every claim links back to its source — students can follow the trail, teachers can grade it.
Hold a conversation that cites every claim it makes. Good practice for the student, useful for the teacher reviewing the trail.
Branch and version a Research notebook for next week's lesson, with sources attached and merges when two threads converge.
Hand out a Code project where students pair with the coding agent — it works alongside, not instead of, the learner.
Build the week's reading from deduped, multi-source news clusters. The world becomes the textbook, with citations.
Reading lists, drafts and rubrics live in versioned folders the rest of the workshop can search semantically.
Courses, progress, certificates. Learning that adapts to how you work.
Drop a file, ask a question, get a chart. No formulas required.
Sketch a term plan from a learning objective. The Writer drafts the unit outline, the Researcher attaches readings to each lesson, the Summariser builds the one-page recap a substitute can teach from. Editable, versioned, ready for the department head review.
Sit beside a student working on their independent project. The workshop questions before it answers — pushing for the source, the assumption, the alternative reading — and never claims a fact it can't cite. The trail of work is the assessment artefact.
A class of thirty, each on their own thread, each at their own pace. The Tutor agent holds the line on rigour — Socratic where it should be, direct where the student is stuck — while the teacher dashboards see who's stalled and where.
Drop a submission against a rubric. The workshop suggests a band, marks the rationale next to each criterion and flags passages it can't fairly judge. A first pass that respects the teacher's final call — never a hidden one.
The Sunday-evening lesson-prep loop, on four shipping workspaces.
Skim the week's deduped multi-source news clusters. The same story read four ways collapses into one — exactly the teaching moment you want when the syllabus says 'evaluate sources'.
Pull the cluster into a Research notebook. Branch a thread for each angle — economic, ethical, technical. Citations are first-class, so the case study models the citation discipline you want from students.
Open a Code project. Pair with the coding agent to turn the underlying numbers into a chart students can read in five seconds. The agent runs the formatting passes alongside; you keep the editorial call.
Export the case study and the chart into the term's versioned Storage folder. Next year's class starts from the artefact, not from a fresh search — and the version history shows what you changed.
askFinz is not your SIS, your LMS or a grading platform. We don't hold roll, publish marks or own the syllabus. Edu is on the roadmap, not in your hands today. What the workshop produces is the case study, the chart, the cited reading list you would otherwise build by hand on a Sunday evening — the artefact a teacher walks into class with. Your school's record-keeping stays where it is.
Tell us about the cohort, the subjects and the term. We'll be honest about what already fits and what is still on the roadmap.
