Skip to content

feat(orchestrator): memory architecture — the axes §7 does not have - #9

Merged
sshlg merged 2 commits into
mainfrom
feat/memory-architecture
Aug 27, 2026
Merged

feat(orchestrator): memory architecture — the axes §7 does not have#9
sshlg merged 2 commits into
mainfrom
feat/memory-architecture

Conversation

@sshlg

@sshlg sshlg commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

SKILL.md §7 gives four memory layers and their lifetimes. Lifetime is one property of a memory system, not its taxonomy — and the survey this file pins says so directly: long/short-term is "proven insufficient to capture the diversity and dynamics of contemporary agent memory systems." Short- and long-term behaviour emerges from how often formation, evolution and retrieval run, not from which box a thing was filed in.

Three gaps, each measured against what the pack already shipped

Retrieval had 2 mentions across 1,938 lines of references. It is four decisions, not one: whether to retrieve at all and from which store · what query to retrieve with · which strategy runs the search · what actually reaches the prompt.

The first matters most and is the one nobody instruments. An agent that overestimates its own knowledge and skips retrieval produces a confident answer built from nothing — no error, no empty result, no latency spike. Invisible to every check that watches for failures.

Facts were not separated from experience, and facts split again by entity. Layers 3 and 4 are experiential — earned from contrast (§8). Nothing in them is a factual store, and a stale fact about the user makes the agent rude while a stale fact about the environment makes it wrong. One expiry rule for both is wrong twice.

Forgetting was decay only. Frequency-based eviction is the easy one to reach for and the one that eliminates long-tail knowledge — the rarely-read entry that prevents the rare expensive mistake. Where storage is not the binding constraint: demote, not delete.

Also carried

  • Forms other than token-level, with their costs: parametric memory cannot be selectively deleted (collides with a right to be forgotten); latent memory cannot be inspected.
  • Shared memory ≠ agent-sync. Leases decide who may write a file now; they say nothing about whose experiential memory is trustworthy enough to act on.
  • Trustworthy memory, three pillars. Abstention under low-confidence retrieval needs a similarity floor to be expressible at all — semantic search always returns K results, so an empty store and an irrelevant one look identical to the model.

What it does not claim

No benchmark numbers reproduced. The frontier sections are frontiers, not practice. It was written from the survey, not from running these systems — where the pack has its own measured experience it stays marked as the pack's.

Discoverability, measured

Against the query "agent memory architecture: forms, functions, dynamics, retrieval, forgetting" this skill ranked 8th among installed skills and now ranks 1st — four distinct term hits against two for the next entry. Description moved 964 → 965 chars, inside the 970-char working limit this repo enforces below the 1024 cap.

(The first attempt to measure this reported the rank getting worse. That was a broken extraction regex returning an empty description, not a real result.)

Source pinned with a read date: arXiv:2512.13564v2, 13 Jan 2026 · read 2026-08-27.

🤖 Generated with Claude Code

NGHTBOY and others added 2 commits August 27, 2026 16:04
§7 gives four memory layers and their lifetimes. Lifetime is one property of a
memory system, not its taxonomy, and the survey this file is pinned to says so
directly: long/short-term "proven insufficient to capture the diversity and
dynamics of contemporary agent memory systems". Short- and long-term behaviour
emerges from HOW OFTEN formation, evolution and retrieval run — not from which
box a thing was filed in.

Three gaps this closes, each measured against what the pack already shipped:

Retrieval had TWO mentions across 1,938 lines of references, and it is four
decisions rather than one: whether to retrieve at all and from which store, what
query to retrieve with, which strategy runs the search, and what actually
reaches the prompt. The first is the one that matters most and the one nobody
instruments — an agent that overestimates its own knowledge and skips retrieval
produces a confident answer built from nothing, with no error, no empty result
and no latency spike. It is invisible to every check that watches for failures.

Facts were not separated from experience, and facts split again by entity. §7's
layers 3 and 4 are experiential — earned from contrast, per §8. Nothing in them
is a factual store, and a stale fact about the USER makes the agent rude while a
stale fact about the ENVIRONMENT makes it wrong. One expiry rule for both is
wrong twice.

Forgetting was decay only. Frequency-based eviction is the easy one to reach
for and it is the one that eliminates long-tail knowledge — the rarely-read
entry that prevents the rare expensive mistake. Where storage is not the binding
constraint the rule is demote, not delete.

Also: forms other than token-level exist and carry different costs — parametric
memory cannot be selectively deleted, which collides with a right to be
forgotten; latent memory cannot be inspected. Shared memory in a multi-agent
system is not what agent-sync provides: leases decide who may WRITE a file now,
and say nothing about whose experiential memory is trustworthy enough to act
on. And trustworthy memory is three pillars, of which abstention under
low-confidence retrieval needs a similarity floor to be expressible at all —
semantic search always returns K results, so an empty store and an irrelevant
one look identical to the model.

The file states what it does NOT claim: no benchmark numbers are reproduced, the
frontier sections are frontiers rather than practice, and it was written from
the survey rather than from running these systems. Where the pack has its own
measured experience it stays marked as the pack's.

Discoverability, measured rather than asserted: against the query "agent memory
architecture: forms, functions, dynamics, retrieval, forgetting" this skill
ranked 8th among installed skills and now ranks 1st, on four distinct term hits
against two for the next entry. The description moved from 964 to 965 chars,
inside the 970-char working limit this repository enforces below the 1024 cap.

Source pinned with a read date: arXiv:2512.13564v2, 13 Jan 2026, read 2026-08-27.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…eference

The house auditor refused the first attempt: SKILL.md's body was 4708/4750
tokens on main, and the new memory section pushed it to 4981. The rule names
its own remedy — "the next section will breach it, and the answer then is a
split, not a trim" — so the answer is not a shorter pointer.

The context-budget trap, layer 0 carryover and workspace scale are memory
ARCHITECTURE, and a file about memory architecture now exists. They move there
as §5.5, beside the retrieval stage where a budget-blind retrieval does its
damage. §7 keeps the four-layer table, the one line that says lifetime is not
the taxonomy, and one pointer.

Body is now 4659/4750 — 49 tokens BELOW where main sat before any of this,
because the split moved out more than the pointer brought in. 0 GAP, 14 PASS.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@sshlg
sshlg merged commit d9ffced into main Aug 27, 2026
2 checks passed
@sshlg
sshlg deleted the feat/memory-architecture branch August 27, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant