Skip to content

Post-compaction note: tell the model what durable state survived (files, goal, todos, transcript) #411

Description

@justrach

From the prime-agent analysis. The single most load-bearing piece of their compaction design is telling the model what persists: every summarization request carries a note ("the kernel keeps running; record names worth remembering"), and after compaction the host injects ground truth ("these names are still defined: ...").

graff analog (no kernel needed):

  1. Append a note to the compaction summary request: files on disk, goal/todo state, and the session transcript all persist; record paths and state worth remembering in the summary.
  2. After compaction, inject a short system note with the actual durable state: active goal + todo items, files modified this session, transcript path.

Notes: touches the same area as #379 (empty-summary escalation). Mind the line caps: agent_compact.zig sits at 598/600 — new logic likely needs its own module (test-root hook wiring per the usual gotcha).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions