The timestep as a transaction: model.step and a run transcript you can watch, publish and read back - #716

Open

lmoresi wants to merge 12 commits into

developmentfrom

docs/timestepping-pattern

Commits on Sep 15, 2026

docs: the timestepping pattern — the clock lives on model.tracker, units are chosen before the mesh

lmoresi
and
claude
committed
44f3615
feat: model.step(dt) — the timestep as a transaction, with an ordered record of what it did

lmoresi
and
claude
committed
6f7421c
feat: a run keeps the state each step started from, writes its log to disk, and draws it

lmoresi
and
claude
committed
e0bcdbc
feat: the transcript — what a run did, judged by a later pass rather than in the loop, and left by default

lmoresi
and
claude
committed
9e82d40
feat: solvers describe what they solve, the transcript records how each solve went, and the figure marks it

lmoresi
and
claude
committed
6526eff
fix: what using the record turned up — two histories on one field, swarm advection, one solve one event, the warnings shim

lmoresi
and
claude
committed
3185edb
feat: the transcript reads as the user wrote the model, with a key to what each part solves

lmoresi
and
claude
committed
e5a372c
feat: the figure's key sets each quantity as mathematics

lmoresi
and
claude
committed
bfad650
feat: the path within a step is stepped, not sloped

lmoresi
and
claude
committed
6b66f13
feat: the figure's key sets each part's residual forms as equations

lmoresi
and
claude
committed
7319c20
fix: exact constants in the transport scheme's form

lmoresi
and
claude
committed
8d169f2
Move the run-transcript blog post to the blog branch

lmoresi
and
claude
committed
d6333c3