sign-lang memory profile

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

Comparison rationale

The inventory is the maintained canon and its persisted replacement products, not all storage in SIGN. The source record describes caller-maintained files; the compile route establishes deterministic replacement of derived files. The shipped corpus is evidence of an available source instance, not a history of learning. Static authoring guidance and executable validator rules are excluded as memory; merely reusing shipped instructions would not establish accumulation through use. See MEM-OBJ-canon-source, RT-RTE-compile-canon and MEM-OBJ-skill-reference.

The reconciliation supersedes the epistemic source, index and bundle records with their memory counterparts. All classifications cite those canonical memory objects. The epistemic combined manifest/checksum remains a valid aggregate, not a superseded competing object; this profile uses the separately declared memory parts. Infer blocks and edge-provenance text remain source parts, not independently learned stores. See MEM-OBJ-canon-source, MEM-OBJ-canon-index, MEM-OBJ-canon-bundle, MEM-OBJ-canon-manifest, MEM-OBJ-bundle-checksum, EPI-OBJ-infer and EPI-OBJ-edge-provenance.

Index reduction warrants consolidation, even though its prose summary was supplied by the source author. It does not warrant synthesis. Raw bundle assembly and sequential replacement do not by themselves establish evolution, deduplication or invalidation: inactive bytes can remain in a contributing mixed-status file, and already-loaded host material is not revoked. Maintenance commands return signals rather than revised retained knowledge. See MEM-OBJ-canon-index, MEM-OBJ-canon-bundle, RT-RTE-source-signals and RT-RTE-corpus-diff.

The documented host route affords instruction and knowledge, with coarse whole-index push followed by requested full-document pull. An ID in that pull does not establish identifier-based push. The same illustrative contract supports these findings; it is not several independent witnesses of deployed consumption. Host parsing, filtering and cache policy remain unresolved. Symbolic source fields separately route deterministic compilation and maintenance; they do not make domain constraints action-enforcing. Metadata has no established later verifier, so byte hashes do not warrant a memory validation/enforcement value. See MEM-RTE-canon-delivery, RT-BAP-canon-guidance, RT-RTE-compile-canon, RT-RTE-source-signals and MEM-OBJ-bundle-checksum.

Software admission establishes automatic output replacement, not manual source approval. Missing initial derivation and approval facts remain local unknowns. No accepted evidenced-absence record warrants a trace-learning negative, and no trace-fed durable behavior-shaping write warrants a positive. Accordingly neither trace-learning nor trace-source receives a controlled finding; this is not an assertion that excluded external systems lack learning. No observed activation, improvement or causal benefit is inferred. See MEM-OBJ-canon-source, RT-RTE-compile-canon and MEM-RTE-canon-delivery.

Source-read log: none. This classification used the supplied accepted members and reconciliation only; no source ambiguity required a direct frozen-source read.