Reflow keeps every course in one AI-maintained folder: planned against the real school calendar, recomputed when the schedule breaks, and published, page by page, to a course site you own.
All caught up
Your site matches your vault. 2 pages are unpublished, which is fine: publish them if and when you want students to see them.
Your vault
Courses
3 lessons · 2 units · 1 assessments
1 lessons · 1 assessments · 2 flagged
The dashboard, on the sample course the software ships with. Real numbers, real interface.
One month of daily use, on five real courses
The problem
Three things eat a teacher's evenings, and none of them is teaching.
An assembly lands on your Wednesday. That lesson moves, the lessons it feeds move, the unit stretches, and the register stops matching. One interruption, eleven edits, every time.
Plans in one folder, slides in another, the schedule in an inbox, three copies of one handout under different names. After a term there is no single current version of the course.
Your course lives inside an LMS the school chose: logins, modules, a layout you cannot change. It serves the institution first, and your students read your work through it rather than because of it.
The folder
Drop sources in; they are never edited. An AI compiles them into course pages, cross-links everything, and keeps one current version of every plan. Add a course and it scaffolds both sides; remove one and it moves to a recoverable trash rather than vanishing.
Courses/ raw/ your files, never edited: syllabuses, schedules, prior plans wiki/ shared/ academic-calendar term dates, holidays, bell schedule classes/ a-level-art-design/ art-appreciation/ media-studies/ overview, unit-plans/, lesson-plans/, assessments/ oxbridge/ pre-a-level-art-design/ index one line per page, so nothing gets lost log every operation, in order, append only
The design follows Andrej Karpathy's LLM wiki pattern: sources stay immutable, the AI does the filing, and the folder becomes a persistent, compounding record of the course instead of a pile of copies. You curate and decide.
The calendar
Term dates, holidays, and exam windows live in one page the tools can read, and every plan is checked against them. Write a date that breaks the rules and you hear about it now, not in December.
Real output, from three bad dates planted in one lesson plan.
It has already caught a live one: a lesson said Thu 3 Sept with an assessment collected at the door, on a course with no Thursday class. Wrong in one place, right in three others. Nobody finds that by rereading.
The reflow
This is the part that is genuinely hard by hand. A week disappears, but the exam window, the portfolio deadline, and the grades date do not move. The question is not what shifts by one week. It is what still fits, and what has to go.
W18 carried a graded assessment. Everything to its right is immovable. Three Wednesdays remain.
Names and codes are from a real course. Nothing here was invented for this page.
If the remaining weeks cannot hold the remaining work, it stops and gives you the options with their costs: compress, move to homework, cut a named topic, use a make-up day. You choose.
Students have been given notice. A date they were promised is treated as almost fixed, and any change to one is raised as a decision for you rather than done as bookkeeping.
"The break removed one Wednesday. Eleven files carried that date. The fix was one conversation."
Doğan Arslanoğlu · art and media teacher, BNDS · built Reflow for his own five courses
The app
Every page shows you what a student would see, with your notes already cut out, and flags anything that still reads like planning before it can publish. One click on. One click off.
Lessons
classes/wos/lesson-plans/wos-w01-is-perception-ever-neutral.md
Assessments
Reads as planning: "TBC"
A course, its pages grouped, and one caught before it could embarrass anyone.
Nothing else in your vault left this machine.
Published 9 of 13 pages (4 without publish: public stayed private, 9 teacher-notes tails stripped) + the site landing page. Reframed for students: 9 from cache, 0 rewritten.
When a check fails, it says nothing was published, and nothing was. A wrong date stops the whole build rather than shipping a wrong promise to students.
Your site
The pages you approve become a clean, fast website that students open like any other link, on any device. No student accounts, nothing tracked, a password on the door. The AI rewrites your planning voice into pages a student can revise from.
Week 1 of 14 · Fri 2026-09-04
At a glance| Core question | Is seeing something we do, or something that happens to us? |
| Reading | Berger, Ways of Seeing, ch. 1 |
| Teacher brings | One image no student will recognize, plus one uncomfortable fact about it, withheld |
Collect descriptions; write the differences on the board without commenting.
Teacher notes: the withheld fact must genuinely discomfort; a neutral caption defeats Movement 2.
Week 1 of 14 · Fri 2026-09-04
At a glance| Core question | Is seeing something we do, or something that happens to us? |
| Reading | Berger, Ways of Seeing, ch. 1 |
| Carried out | If seeing is never neutral, what is a photograph evidence of? |
This lesson asks whether seeing is something you do or something that happens to you. You work with an unfamiliar image, separating what you see from what you know and what you assume.
The ideasSeeing is shaped by what you already know. The central claim comes from John Berger: seeing is not neutral. Two people can look at the same image and honestly report different things.
The same lesson, before and after. Both columns are the real page.
A page reaches students only when you mark it, one page at a time. There is no publish-everything, and the AI is never allowed to mark a page.
Everything below a page's Teacher notes heading is cut structurally before anything else runs. The failure mode is cutting too much, never leaking.
Side by side
| A folder of files | An LMS | Reflow | |
|---|---|---|---|
| One current version of every plan | ✗ | ~ | ✓ |
| Knows your term dates and holidays | ✗ | ~ | ✓ |
| Recovers a lost week, and shows the cost | ✗ | ✗ | ✓ |
| Every change recorded and reversible | ✗ | ~ | ✓ |
| A site you own, that students just open | ✗ | ✗ | ✓ |
✓ yes · ~ partly · ✗ no
Working with it
Syllabuses, timetables, last year's plans, in any state. It reads them, reports what it found, and files the course: overviews, units, lessons, registers. A substantial source touches ten to fifteen pages.
What am I teaching the week the seniors are away. Which units need the darkroom. What did I decide about late work. Answers come from your own pages, with the pages cited.
A cancelled class, a moved deadline, a new timetable. It finds the wall, recomputes what fits, updates every page that carried the old dates, and puts the trade-offs in front of you.
It hunts contradictions, stale claims, dates that disagree with the calendar, and decisions still marked open that your sources have since answered.
The pilot
Starting September 2026, at BNDS. You bring one course. We build the rest together.
One course, your existing files in whatever state they are in, and a Mac or Windows laptop. Nothing needs tidying first.
Your folder, together, from your own materials. The calendar wired in. The site set up if you want one, skipped if you do not.
Two honest numbers: what a setup really costs, and how much of the AI's drafting survives your red pen. Those numbers decide whether this becomes a real product.
You would be among the first users. The folder needs feeding or it goes stale. And the setup cost is the thing we cannot quote yet, which is exactly why the pilot exists.
Or just find me in the art room.