2 posts tagged with "engine"

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.

The scheduling brain of RABS just had its biggest renovation since the project began. The metaphor names everyone learned -- workshed, loom, ribbon -- have done their job and are now retired. In their place sits core_engine: a born-clean Postgres schema with 19 tables, a dedicated instance API at /api/v1/engine, a fully-wired program creation wizard, and a working philosophy for how the past becomes truth. Twelve backend route files were rewritten to point at the new schema. Seventy-three real billing rates replaced the POC junk rows. The wizard now handles NF2F lines, participant photos, participant fees, click-to-edit time slots, and full draft management. None of this is theoretical anymore.