LLM Project Wiki memory profile

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

Comparison rationale

The accepted records describe a prompt-defined file memory design, not an installed runtime. Every positive finding therefore has claimed basis. Complete coverage of a specified inventory does not upgrade its evidence to wiring, operation or benefit. Provider weights and host compaction are outside the memory boundary; unknown delivery of included live rules remains inside it.

Compilation, admission and consumption are separate. MEM-OBJ-sources supports imported reference copies; MEM-OBJ-wiki supports model-authored pages. EPI-OBJ-wiki-pages preserves uncertainty about semantic derivation, so new-page creation is not automatically controlled synthesis or consolidation. Revisions of existing entries do support evolution. Stale marking supports invalidation only at the specified stale-sensitive status consumer, not universal withdrawal; RT-RTE-wiki-lookup and MEM-CLM-retention-limits retain that distinction.

The retained live project rules give Wiki pages relative priority over fallback memory and source at the future question/edit model consumer. This is ranking authority at claimed basis, supported by the ordered flow in RT-CLM-wiki-first, the retained future-session channel in RT-BAP-project-rules and its consumer operation in RT-RTE-wiki-lookup. It coexists with instruction authority for standing directions and routing authority for operation/scope selection. No numerical ranking algorithm is required; actual loading and compliance remain unobserved. Known authority coverage describes these specified effects, not deployed enforcement.

The gap route gives retained experience learning authority at the repair consumer, and its revised page knowledge authority at later lookup. MEM-OBJ-log and the memory annotation on RT-RTE-diff-ingest support the claimed chain without proving improved capacity. Reports of task insufficiency do not establish one of the four controlled original trace sources; no raw conversation, tool recording or state/action/outcome sequence is supplied. Unknown project-memory provenance remains a separate unresolved branch.

Requested index/page/diagnostic reads are pull, even when a model or fixed predicate selects candidates within the request. RT-BAP-project-rules and RT-BAP-maintenance-rules specify future live channels without exposing their host loading operation. This prevents classifying all read-back as pull-only or assigning an unsupported push signal. File paths on requested reads do not establish identifier-based push.

Reconciliation supersedes EPI-OBJ-sources and EPI-OBJ-log with the corresponding memory objects. Findings cite those canonical memory declarations. EPI-OBJ-wiki-pages and EPI-OBJ-index remain valid containers; finer memory parts distinguish domain content, metadata, navigation and health predicates rather than flattening their effects. No classification depends on a superseded record.

Source-read log: no frozen source files were read for this profile. Classification uses only the supplied accepted members and reconciliation; no new evidence or records were added.