Environment: dsh-mnemon 0.5.13 (0.5.14 release notes checked — unrelated), DSH desktop profile, Windows.
Observed: entries in ~/.mnemon/runtime/memories.json each carry content, created_at, updated_at, target, importance. The projected USER.md / MEMORY.md snapshot renders none of them — every entry reaches the agent equal-weight, no grade or age visible.
Why it matters: the control plane deliberately maintains this metadata (the UI edits importance; the write protocol grades critical/normal/low; capacity maintenance reads it) — then the projection discards it at the last hop. The agent consuming the snapshot cannot see data the system itself maintains. This is an information-fidelity gap, not a missing feature: the data already exists end-to-end. Rendering it would not change "historical memory never outranks current instructions"; it only makes the recorded grade/age visible to the reader.
Ask (either works):
- Render
importance and an age indicator in the runtime projection. For age, a relative value computed at projection time (e.g. "14d") seems more useful than a raw timestamp; day-level precision matters — month-level is too weak for fast-moving work.
- Or expose the projection format as configuration/hook so profiles can customize rendering.
Alternatives considered: strategy-light-context caps resident size but is a blind ceiling (no importance awareness, no on-demand expansion) — not a substitute. Patching bundled lib/*.js is upgrade-fragile. A custom Source via extension-sdk works but is heavy for a rendering detail.
Not asking for: relevance gating, token accounting, or delta injection.
Environment: dsh-mnemon 0.5.13 (0.5.14 release notes checked — unrelated), DSH desktop profile, Windows.
Observed: entries in
~/.mnemon/runtime/memories.jsoneach carrycontent,created_at,updated_at,target,importance. The projected USER.md / MEMORY.md snapshot renders none of them — every entry reaches the agent equal-weight, no grade or age visible.Why it matters: the control plane deliberately maintains this metadata (the UI edits importance; the write protocol grades critical/normal/low; capacity maintenance reads it) — then the projection discards it at the last hop. The agent consuming the snapshot cannot see data the system itself maintains. This is an information-fidelity gap, not a missing feature: the data already exists end-to-end. Rendering it would not change "historical memory never outranks current instructions"; it only makes the recorded grade/age visible to the reader.
Ask (either works):
importanceand an age indicator in the runtime projection. For age, a relative value computed at projection time (e.g. "14d") seems more useful than a raw timestamp; day-level precision matters — month-level is too weak for fast-moving work.Alternatives considered:
strategy-light-contextcaps resident size but is a blind ceiling (no importance awareness, no on-demand expansion) — not a substitute. Patching bundledlib/*.jsis upgrade-fragile. A custom Source viaextension-sdkworks but is heavy for a rendering detail.Not asking for: relevance gating, token accounting, or delta injection.