EchoesVault for OpenCode memory profile

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

Comparison rationale

This profile classifies accepted records only. No source files were read, no records were declared and no report finding was revised. All positive bases remain local: deterministic persistence cannot turn requested semantic distillation into an implemented transformation. The model proposal path supports claimed trace extraction, consolidation and trace learning; software admission and later delivery are separately wired. See EPI-RTE-session-distill, RT-RTE-session-save and RT-RTE-context-restore.

The reconciliation supersedes the epistemic daily object with MEM-OBJ-daily, and the epistemic migration route with MEM-RTE-summary-migration. The profile uses those canonical records. The complete-page container and its body/frontmatter parts remain distinct valid records; summary source and derived index likewise remain separate operative parts. These dispositions change citation ownership, not values or evidence strength.

Current page text has two consumers: the host receives knowledge, while replacement preflight uses its digest as a concurrency reference and enforced veto. That narrowly scoped validation/enforcement is independent of factual acceptance. The generated schema and lifecycle grant are not accumulated knowledge and are not used to inflate authority findings. See MEM-OBJ-page-body, RT-RTE-page-upsert and EPI-ABS-semantic-check.

Managed project restoration is pull even though code chooses recent filenames and matching lines inside the request. The periodic TUI is a separate push consumer of persisted bookkeeping; its fixed-field selection supplies coarse signal, not task-relevant targeting. Raw/assets have known file storage but unresolved payload forms, origin, control and consumers. Their uncertainty remains in each affected axis rather than being erased by the better-inspected managed paths. See MEM-OBJ-local-state, MEM-RTE-health-report, RT-RTE-context-restore and MEM-OBJ-source-material.

No observation or causal comparison is supplied. The profile therefore makes no claim of deployed compliance, faithful compression, verified saved facts, complete trace provenance or improved future decisions. Missing initial provenance limits lineage and control, not the known file substrate. Unknown actual input/output content prevents adding synthesis or extra trace-source values; it does not erase the prescribed session-distillation route. See EPI-RTE-session-distill, MEM-OBJ-daily and MEM-OBJ-page-body.