Amm save resume

AMM — Save Resume Point

Purpose

Most agent hosts lose working context between sessions. A resume-point entry captures the current state + pending list + the single next action + files-to-read, so the next session's first turn can restore working context in one memory_recall.

When to Trigger

• User signals wrap-up: "that's enough for today", "let's continue tomorrow", "save state".
• Agent self-detects session end approaching (context near limit, long idle, or explicit close).
• After a major milestone, to bookmark the handoff for the next cycle.

Apply Conditions

• At least one pending item exists (otherwise no need to resume — the session is clean).
• The "next first action" is concrete (not "continue working").
• A short list of files-to-read captures the minimum context restore.

Execute

memory_save({
  content:  "RESUME POINT (#{{SESSION_ID}}, session end):
             [state]   <one-line summary of current state>
             [pending] <bulleted list of unfinished items, with P0/P1/P2>
             [next]    <single concrete first action for next session>
             [read]    <files next session should open, in order>",
  type:     "workflow",
  concepts: "resume_point, {{SESSION_ID}}, <main_topic>",
  files:    "<comma-separated absolute paths in restore-read order>"
})

Warnings

• Do NOT save a resume point when the session finished cleanly (no pendings) — it just adds noise on the next session's start recall.
• Do NOT rely on this for long-term pendings (>14 days). Use amm-save-pending with an explicit TTL, or a proper project tracker.
• The "next action" must be resume-able without the current session's short-term context. If it would require "ask the user what they meant 3 turns ago", revise before saving.

Example

End of a session working on a database migration:

memory_save({
  content:  "RESUME POINT (#delta-7, session end):
             [state]   migration 0042 drafted, review pending, rollback script untested.
             [pending] P0: test rollback on staging.
                       P1: write the up/down migration for the index.
             [next]    run rollback test — psql staging < migrations/0042_down.sql && verify row counts.
             [read]    migrations/0042_up.sql → migrations/0042_down.sql → docs/migration-playbook.md",
  type:     "workflow",
  concepts: "resume_point, delta-7, migration_0042",
  files:    "/workspace/migrations/0042_up.sql,/workspace/migrations/0042_down.sql,/workspace/docs/migration-playbook.md"
})

Related

• amm — umbrella (Bootstrap, references, license)
• amm-recall — how the next session retrieves this entry
• amm-save-pending — per-item tracking with TTL

Change Log

• 1.0.0 — Initial release.