The Engine Roadmap: Where We Are and What Comes Next
· 7 min read
Three weeks ago the scheduling core got a born-clean schema and a working wizard. The engine can build a blueprint, fan it out into date-specific instances, and lock those instances as historical truth when the day is done. That is real and running. But the operational half — the half where people cancel a participant for one Tuesday, pull a bus mid-week, override a billing line, and then ask "why is Nathan not on Saturday?" — is still a design document. This post maps the territory between where the code ends today and where the design says it needs to go.