Momentum · Featured · Local continuity
TACTICO Momentum — The process died.
The goal did not.
Agents continue through a local MCP. Operators inspect the trail on a map. The core stores versioned goals, typed memory, checkpoints, and a verified resume. It preserves context. It does not choose what the agent should want.
goal / release-2.4.0Resume verified
- goal.createdstream 3
- memory.writtentyped
- checkpointhash 7f3c
- process.exitworker lost
- goal.resumedhashes match
Labelled synthetic fixture · not live agent state
The continuity model
A goal survives the worker.
The core holds a versioned stream of the state an agent needs to continue. A restart loads a verified resume bundle instead of asking the next process to reconstruct intent from a transcript.
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.
Tactico product system
Different problems. One standard of honesty.
Context should stay useful—and under your control.
We compute locally when we can, make hosted participation explicit, and state coverage and availability as they are.
Meet Tactico Technologies