Every session runs the same four steps in the same order. The last step of one session feeds the first step of the next, so the work carries forward without anyone holding it in their head. Here is the rhythm.
ORDOVA ⚑ session · 3 issues at startup
▸ wrap-up · 3 breadcrumbs claimed → dispatch /wrap-up-finalize
⚑ portability · 1 link to a local-only path (~/notes/) → lift before they accumulate
⚑ sync · dirty tree blocks fast-forward (2 modified, 1 untracked) → commit/stash or /wrap-up-finalize
A fresh context starts and picks up the breadcrumb left behind.
The deferred wrap-up from the previous session completes in the background, picking up again if a prior run stalled.
The session runs, with checkpoints saved along the way.
A breadcrumb is written and the rest is handed off to next time.
The work of closing a session splits in two. One part runs now, while you wait. The other is deferred and finishes at the start of the next session.
Runs the moment the session ends, while you wait. It captures the essential state, grounded by a running log of the session's outward actions, and writes the breadcrumb, then returns. Fast by design.
Picks up the breadcrumb at the start of the next session and finishes the slow work in the background. Nobody waits on it.
Saves progress mid-session, so a long run never loses its place.
Hands off at the end, fast, leaving a breadcrumb for next time.
Finishes it next time, in the background, before the new work begins.