JEPA-Anything memory profile

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

Comparison rationale

The builder retains products and bounded numerical history, not a target-owned agent-session store. The profile keeps generated executable constants separate from copied assumptions, diagnostic feedback and file-list metadata. The first have fixed-rule consumers; inspectability of the others does not establish a later semantic consumer. See RT-OBJ-scaffold-manifest, RT-BAP-generated-contract and MEM-OBJ-compiler-assumptions.

The supplied reconciliation leaves missing-part conflicts for diagnostic feedback, generated executable contracts and the generated file-list manifest. This profile does not declare replacements or reopen verification. It cites existing containers and their recorded paths, preserves supported findings, and leaves affected inventory coverage partial. It neither grants a report the generated program's authority nor treats the whole package as a single fully assessed consumer object. Consequently no complete-value enumeration is claimed for those axes.

The supplied reconciliation supersedes the epistemic variance object and route with MEM-OBJ-online-variance-tracker and MEM-RTE-streaming-monitor. All profile references use these canonical declarations. Welford buffers are symbolic sufficient statistics under fixed consumer rules, not parametric encoder weights. The reset operation is forgetting; it does not establish gradual decay, history-preserving invalidation or per-sample deletion. EMA and QR revise existing numerical state. None of these operations establishes improved capacity. See also MEM-CMP-target-encoder and RT-RTE-core-projection.

The trace-learning positive is deliberately only claimed. The source-defined workflow asks the host to consume tool diagnostics, revise the design, retain it and render contracts that later calls consume. That meets the profile's trace-fed artifact-write meaning at the requested-workflow layer; it is not an assertion of observed training, autonomous orchestration, a revised Skill or compiler self-improvement. The numerical histories retain separate unknown provenance and durable-write limits. A diagnostic-repair positive does not classify those alternatives. See RT-RTE-task-compilation, EPI-RTE-design-diagnostics, RT-RTE-scaffold-admission and RT-BAP-generated-contract.

A requested path load, module call or manifest verification is pull. Internal delivery within that requested operation is not counted again as push. File paths and module identities do not establish identifier-based unsolicited selection. Since later semantic report/assumption consumers remain unresolved, the signal axis is not globally inapplicable. The unpublished checkpoint entry is metadata only; the verifier's future published-file branch is integrity checking, while verify-before-load is an afforded external consumer role. See MEM-OBJ-checkpoint-manifest, MEM-RTE-streaming-monitor and RT-RTE-scaffold-admission.

No frozen-source files were read for this classification. All warrants come from the supplied records and annotations, with the supplied reconciliation resolving the two supersessions. No records, quotations, source identities or execution evidence were added.