Each schedule is a private repository: the documents, the people, the rules, the model, and the results — one attributed, append-only history. Clone it to plain files, edit in any editor, push back. Like a git host, for the operational truth behind a schedule.
1. Create an account — your username becomes your namespace (you/schedule).
2. On your dashboard: mint an access token and install the form command (one pip line, shown there).
3. Then, from your terminal:
form new first-schedule example # a worked starter; your namespace is implied cd first-schedule form push -m "my first change" # like git — no path needed
description.md the problem in plain words entities.json who is being scheduled constraints.json the rules model.smb the solver model
Every push becomes attributed commits; history is never rewritten or deleted. Every repository is private to its owner.