RepoCodex memory profile

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

Comparison rationale

The comparison concerns accumulated repository memory, not every persistent file installed by the runtime. Static skills supply the write/read protocol but are not an additional memory instruction registry. Files hold explanations and access structures; Git history supplies bootstrap's activity input. Metrics remain a separate, usually ignored file store. The operative inventory is supported by RT-OBJ-concept-body, RT-OBJ-concept-frontmatter, MEM-OBJ-context-catalog, MEM-OBJ-context-log, MEM-OBJ-reverse-index and MEM-OBJ-metrics.

Mixed parts and consumer-specific authority

Prose explanations supply knowledge to coding agents. Body-link targets and parsed frontmatter supply symbolic selectors and criteria. Sources and stamps also affect rank without authenticating content. Persisted reverse-index copies are checked for synchronization; retrieval reconstructs current mappings rather than loading those copies. These forces must not be collapsed into one knowledge or enforcement value: see RT-BAP-memory-consumption, MEM-CLM-context-selection, MEM-OBJ-reverse-index, EPI-RTE-impact-read and EPI-RTE-claim-check.

Deprecation is invalidation with history retained, not global deletion. It enforces ordinary body exclusion but does not prevent direct reads. Reanchor evolves existing evidence pointers; identity relocation alone preserves body bytes and does not establish semantic curation. Draft-to-stable normalization is a tier promotion. No observed semantic synthesis, consolidation or deduplication follows from a repair command name, import wrapper or primary-key check: see RT-RTE-memory-write, RT-RTE-anchor-patch, RT-RTE-relocate-identity, EPI-RTE-audit-gc and MEM-RTE-concept-read.

Requests versus unsolicited selection

All established local later-consumer routes are requested reads or requested computations. Path/identity matching inside a requested context return is pull, not an additional push. Audit sampling, impact traversal and validation loading likewise fulfill an explicit command request. The record inventory supplies no independent unsolicited injection route within this boundary. Consequently read-back signal is inapplicable here, not identifier merely because a requested identity is exact. The relevant warrants are RT-RTE-context-read, MEM-RTE-concept-read, RT-RTE-review-audit, EPI-RTE-impact-read and MEM-RTE-metric-readback. Host injection and provider retention are outside this inventory, not classified as absent.

Trace-fed artifacts without demonstrated benefit

The bootstrap history branch selects recorded change subjects, automatically persists drafts and exposes them to later draft-enabled or direct readers. This supports wired trace learning under the profile's artifact-update definition, with event-stream origin and trace-extracted lineage for that history subset. Its update consumer has learning authority; the resulting explanation supplies knowledge downstream. The comment/document branch instead imports static authored text. A last-touch commit pointer does not transform that text's origin into an activity trace. Import and trace extraction describe distinct provenance aspects of the history branch, not a new semantic inference: see RT-RTE-bootstrap-drafts, EPI-RTE-bootstrap-import and EPI-OBJ-bootstrap-body.

The coding skill affords a second, weaker route from validation feedback to retained explanation revision. Its tool-feedback origin remains separate from the wired bootstrap witness. No trace establishes actual foreground revision or improved capacity. The repair subprocess remains unresolved: process success neither identifies its inputs nor certifies a durable update. Metrics supply a diagnostic ratio, not an inspected policy-update consumer. These distinctions follow RT-RTE-coding-loop, RT-RTE-validate-change, RT-RTE-agent-repair and MEM-RTE-metric-readback.

Partial trace-learning coverage retains a supported system-level yes but licenses neither a complete learning inventory nor a no. No accepted evidenced-absence record warrants a local no for the diagnostic or arbitrary-content alternatives. Original authorship, explicit human control on direct/initial writes, actual repair transformations and any additional semantic authority of their payloads remain unresolved rather than borrowing the strongest witness from another route.

Reconciliation and inspection limits

The supplied reconciliation makes no supersession amendment. Valid containers and their declared parts remain canonical; no comparison value depends on replacing a record. It separates path retrieval from direct identity reads and index reconstruction from persisted sync-check copies. Possible shard identity collisions limit unambiguous addressing, not the existence of retained file memory. The local warrants are RT-RTE-context-read, MEM-RTE-concept-read, MEM-OBJ-reverse-index and RT-OBJ-concept-frontmatter.

Source-read log: none. This profile classifies the supplied accepted records only. No source ambiguity required a frozen-source read. All positive bases remain implementation wiring or afforded protocol routes; no observed or causal finding is inferred. Unknown provenance and repair behavior prevent stronger coverage where explicitly named, while external hosts are excluded consistently rather than treated as opaque local stores.