Versioned goals
Lifecycle, criteria, and constraints. Completion is blocked while required evidence, subgoals, or open conflicts remain.
Momentum · Local continuity · In development
Momentum — The process died.
The goal did not.
Momentum is a continuity layer for long-horizon agents: versioned goals, typed memory, atomic checkpoints, and a verified resume.
See the continuity modelCONTINUITY_CONTEXTrelease-2.4.0
- stream
- 3 · expected
- checkpoint
- 7f3c · verified
- bundle
- goal · memory · conflicts · drift
- resume
- ready
Synthetic fixture · not live agent state
Verified resume
A stream you can resume from.
The core is the authority. Every accepted change checks the expected stream version and writes in one transaction. A restart loads a verified resume bundle: the goal, visible memory, open conflicts, drift, and an optional checkpoint. Missing or changed hashes are an integrity error, not a silent skip.
Momentum
Work returns with its reasoning intact.
Continuity is structured: versioned goals, typed memory, atomic checkpoints, and a verified resume.
- 01 · GoalVersioned goalExpected stream version
- 02 · MemoryFour memory kindsTyped and explicit
- 03 · CheckpointAtomic checkpointOne transaction
- 04 · ResumeVerified ResumeBundleHashes checked before trust
Goal recordExpected stream version
prepare-release
Every accepted change checks the expected stream version before one transaction writes the result.Attached memoryFour kinds
- WorkingShort-lived keyed task context.
- EpisodicObservations and actions with an occurrence time.
- SemanticSubject / predicate / object claims with confidence.
- ProceduralReusable procedures with ordered steps.
A ResumeBundle loads the goal, visible memory, open conflicts, declared drift (allow, warn, or block), and an optional checkpoint. Hash mismatch is an integrity error, not a silent skip.
One committed stream
A stream you can resume from.
Typed memory
Working, episodic, semantic, and procedural records. Shared or private. Supersession and conflicts are explicit, not inferred from prose.
Atomic checkpoints
Progress, working state, memory writes, and a state hash in one commit. Resume verifies those hashes before trusting the snapshot.
Exact resume
A ResumeBundle plus a hash-based manifest. Missing or changed checkpoint data is an integrity error, not a silent skip.
Declared drift
Hard-rule checks on a supplied action snapshot. Allow, warn, or block—recorded, not cleared by a later benign check.
Surfaces
Agents continue. Operators inspect.
The same continuity contract appears through a local MCP for agents and a labelled Console fixture for operators. Hosted surfaces are not generally available.
Local stdio MCP
Local stdio over SQLite, identity bound at process start, twenty-one typed tools, and zero product telemetry. Hosted MCP has not shipped.
Labelled Operator Console
A continuity map, a cockpit for the next safe action, and an evidence inspector. The browser fixture is not an authenticated live account.
Local MCP
Local stdio tools over the same SQLite-backed core. No hosted Momentum endpoint.
Local Console
A labelled local operator workspace concept. Not a live account.
CLI
Workspace-scoped goals and memory from the terminal. Not generally available.
Python SDK
The same local contract as a typed client. Not a public package today.
The store is the continuity you wrote.
Goals, memory, and checkpoints stay in the local SQLite store you control. Momentum does not create a hosted dossier of Pathways walks or Ionic contracts, and the Console does not call a Tactico API from the browser.
It remembers. You decide.
You choose the goalMomentum resumes what you checkpoint. It does not choose objectives or run tools for you.
It stays localGoals, memory, and checkpoints remain on your machine. There is no hosted continuity service.
Local continuity · no hosted service