OpenViking memory profile

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

Comparison rationale

This profile classifies accepted records, not new source evidence. All ten axes remain partial because the recorded boundary retains unresolved included producers, payloads or consumers. A known unit covers its named part only. It does not resolve an alternative merely because the alternative shares a file format, updater or service endpoint.

The raw archive, derived overview, checkpoint, external tool payload and access metadata remain distinct parts. The valid container RT-OBJ-session-commit is not replaced by MEM-OBJ-archive-overview or MEM-OBJ-checkpoint. Reconciliation proposes no supersessions; therefore no value depends on replacing an ID. Likewise, memory assertion fields and experience instruction fields overlap file content without replacing the complete file/policy objects. Numerical index representations are parametric form on vector storage, not evidence of local weight learning: MEM-OBJ-memory-index.

The memory boundary includes opaque tool and skill payloads. Their file substrate is known while their actual consumed form remains unresolved. A readable display synopsis does not classify a hydrated original: MEM-OBJ-tool-result. Initial caller content and explicit administrative choices retain unresolved write agency. No manual classification follows from a route called manual, a generic caller, or a request to confirm forgetting: MEM-RTE-resource-withdrawal. The corrected account-template account separates managed edits from persisted-template consumption. No embedding-template editing capability or blanket human-curated lineage is inferred from the index consumer.

Authority follows the actual retained part and consumer. File text supplies context; experience directions supply instruction; prior policy and trajectory content feed durable revision; embeddings/abstracts affect ranking; identifiers and status state route work; the ledger vetoes recent delivery; retained target/link content supplies mechanical validation and deletion vetoes. These forces do not establish truth acceptance, compliance or benefit. The schema's requested system-prompt channel remains claimed alongside the wired VikingBot user-role reminder: EPI-OBJ-experience-instructions, MEM-BAP-experience-reminder.

Curation follows implemented effects. Summary/standing-fact extraction consolidates, field replacement evolves, and successful removal forgets entries within the controlled decay meaning. Deletion does not by itself establish history-preserving invalidation or universal revocation. Compile explicitly requests deduplication, but its model-mediated semantic result is unobserved; that finding stays claimed rather than borrowing wiring from the physical updater: EPI-RTE-memory-consolidation. There is no supported synthesis finding merely because a model generalizes or because semantic preservation is unresolved.

Requested database returns are pull. Automatic host augmentation is push; both occur within one chain rather than competing as system-wide labels. Automatic hydration is a distinct identifier-selected supply into extraction input. OpenCode recall combines coarse gates/budgets, semantic candidate selection and optional model omission/rewrite. VikingBot's links actually select delivered experience bodies, unlike a bare URI in a catalog: RT-RTE-plugin-recall, MEM-RTE-bot-recall, MEM-RTE-tool-externalization. Requested session reconstruction does not become an additional push merely because code selects summaries or inserts anchor checkpoints.

Trace learning here means automatic trace-fed durable artifacts with later consumers, not demonstrated improvement. Continuation summaries qualify alongside standing memory and reusable policies. The reports' independent uninspected learning/theory/reflection conclusions do not negate this architectural write-route classification: MEM-RTE-session-reconstruction, MEM-RTE-experience-maintenance, EPI-RTE-policy-training. Tool capture contributes tool-traces where it actually feeds those writes. Event callbacks transporting conversational messages do not create an event-stream source; a derived object named Trajectory does not establish the original linked state/action/outcome source class. Optional evaluator inputs and alternative producer paths retain uncertainty rather than being excluded to obtain a known union.

Source-read log: no source files were read. Classification uses only the supplied accepted records and their annotations, with reconciliation used to resolve identities. No evidence passages, analyst records or source facts were added.