VLM-wiki memory profile

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

Comparison rationale

The memory inventory is the accepted memory member's object inventory, not every storage or authority surface in the enclosing runtime. A Git checkout does not by itself turn file memory into a repo substrate. Shipped agent instructions and configuration constrain operation but are not accumulated through use. External provider weights are opaque components, not an established trace-updated memory alternative within this scoped repository mechanism. See MEM-OBJ-raw-inputs, MEM-OBJ-import-manifest, MEM-OBJ-runtime-briefs and RT-CMP-qwen.

Assessment describes coverage, not activation. The known file and curation inventories do not claim observed use or semantic accuracy. Form coverage is partial: implemented output encoding is distinct from claimed host reading, wired work-preview delivery, afforded historical delivery and unresolved later readers of briefs, helper labels, reports and logs. Claimed host operations stay distinct from wired Python operations; unknown initial content control prevents complete lineage and agency. A missing later consumer prevents an authority finding, not a storage finding. The parser and navigation limitations remain material: MEM-CLM-parser-projection and MEM-CLM-index-targets prevent equating an on-disk article with faithful report or answer context.

Curation and trace learning are independent. Consolidation reduces retained fields; fixed rules also synthesize unsupported interpretive claims, as established by EPI-RTE-history-interpretation and EPI-RTE-work-interpretation. The work activity-to-page/advice-to-later-consumer chain qualifies locally as trace learning even though it neither rewrites Python nor demonstrates better future capacity. Other origins and output consumers remain unresolved. Imperative advice is knowledge at its human consumer, not automatically standing agent instruction. No semantic acceptance or causal benefit is implied.

Read-back distinguishes the consumer request from downstream unsolicited supply. Host relevance selection stays on a requested pull route. Preview-section and fixed-budget sender selection supplies a coarse push, not identifier targeting merely because the sender receives a file path. Historical delivery has only its documented caller warrant, and its fallback does not select the intended embedded preview: RT-RTE-wiki-query, RT-RTE-work-cycle, MEM-CLM-daily-delivery.

Reconciliation supersedes the epistemic image-metadata route with MEM-RTE-metadata-extraction; all profile references to that preparation/read-back mechanism use the surviving record. Other overlapping containers and epistemic parts remain valid separate referents. No other supersession changes a classification.

Source-read log: none. This profile classifies supplied accepted records only; it adds no source quotation, record, execution or evidence layer.