Why it exists
Agentic coding sessions lose their through-line. Work spans more than one context window, and detail evaporates across compactions and fresh windows. saga is the orchestration layer that strings a body of work into one coherent session — owning neither knowledge nor work itself, but threading the two domain tools beneath it: norn for knowledge, mimir for work.
It came out of a restart. An earlier single-tool design got bent when task-workflow concerns invaded the decision space — so orchestration was split out into its own layer.
What it does
- start-session — assembles the session primer (user profile + shared memory + workspace brief) and routes the work; reloads on each resumption to hold the through-line.
- grill-me — Socratic interrogation that pressure-tests a plan against the workspace’s glossary and recorded decisions.
- write-session-log — at a work boundary, writes the merged log of decisions, deviations, and consolidation candidates.
- consolidate-sessions — lifts durable lessons out of frozen logs into maintained context.
- initialize-saga — binds a project to a vault workspace and scaffolds or self-heals it.
The session log is the record
saga deletes a category. Specs and plans are transient review surfaces, discarded on merge; the one durable retrospective is the session log — itself prunable once its lessons are lifted out. The test for keeping anything is blunt: would it matter if this were deleted? It’s also the test the whole tool family passes — state your purpose without an “and.” norn keeps knowledge. mimir holds work. saga weaves them into a session.