REM memory profile

Type: agentic-system-analyses/types/agentic-system-memory-profile.md

Comparison rationale

The profile separates an operative retained part from the mechanism that proposes it. Episode text, metadata, vectors, temporal topology and access counts have conditional wired persistence and later consumers. Semantic schema and storage helpers are capabilities; a generated candidate is not a retained semantic instance. Unknown semantic population therefore limits lineage and admission control without obscuring the known storage encodings and conditional read consumers. See MEM-OBJ-semantic-control, MEM-OBJ-memory-vector, MEM-OBJ-memory-graph, EPI-OBJ-semantic-result and RT-ABS-writeback-routes.

The reconciliation supersedes the epistemic raw-content and parse-fields records with MEM-OBJ-raw-content and MEM-OBJ-episode-interpretation. Their source-truth and semantic-fidelity limits survive; these identity supersessions do not strengthen any finding. The candidate container, candidate text, attached lineage, SQL representation and retrieved payload remain distinct. No retained payload is classified as engine-produced solely because the names match. See MEM-OBJ-semantic-candidate, MEM-OBJ-semantic-lineage and EPI-OBJ-semantic-result.

A host requests read-back. Automatic ranking within that request is not a second push operation. Listing, worker fetches and cache reuse also fulfill requests. Thus read-back signal is inapplicable across the named direction inventory, not unknown merely because no SDK handoff succeeds. Go constructs context for a direct HTTP consumer, but ordinary nonempty SDK results fail required timestamp conversion before either adapter delivers context. Knowledge authority at server construction and conditional host consumption remains distinct from successful host activation. See RT-RTE-context-retrieve, MEM-RTE-memory-listing, RT-RTE-host-integration and RT-BAP-context-injection.

Trace learning here means an automatic activity-fed write with a durable behavior-shaping result and later consumer, not demonstrated improvement. Session-derived metadata and vectors have later selection consumers; retrieval events produce durable counters used by the reranker. These are different original sources and different update mechanisms. Retaining raw messages alone is not that transformation. Direct consolidation and the alternative compressor return candidates without retaining them. The claimed semantic loop stays claimed because its automatic durable admission is disconnected. Local negative units do not erase supported positive routes or justify a system-wide negative. See MEM-OBJ-episode-interpretation, MEM-OBJ-memory-vector, EPI-RTE-retrieval-feedback, RT-RTE-direct-consolidation, EPI-RTE-compressor-helper and RT-CLM-memory-loop.

Recency weighting is decay because it downweights retained episodes. Count feedback is promotion because it raises their later salience. Requested semantic abstraction receives only a claimed consolidation finding: model outputs and their preservation of claims are not supplied, and the task does not complete persistence. The broader self-evolving and forgetting claims retain their own design-level findings, not the wired witness from count feedback. No synthesize finding follows from epistemically indeterminate model output, and no invalidate finding follows from unused lifecycle flags or attempted reset. See RT-RTE-context-retrieve, MEM-OBJ-retrieval-count, EPI-RTE-pattern-extraction, EPI-CLM-recursive-memory and MEM-ABS-memory-withdrawal.

Unknown generic caller origin prevents a complete lineage or trace-source inventory. Unknown initial semantic admission prevents manual/automatic and prior authority conclusions for that branch. No operator decision is inferred from workflow launch or source authorship. Static provider weights and shipped extraction guidance are excluded from accumulated memory, while returned dense embeddings remain included. No observed or causal basis is assigned: no execution evidence is supplied. See MEM-OBJ-raw-content, MEM-OBJ-semantic-control, RT-RTE-episode-write and RT-CMP-embed-service.

Source-read log: none. Classification used only the supplied accepted members and reconciliation; no source ambiguity required a direct source read, and no incumbent or reference profile was consulted.