{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-avoid-promoting-episodic-traces-into-semantic-memory-during-retrieval-augmented-consolidation",
  "title": "Under what conditions must an instance avoid promoting episodic traces into semantic memory during retrieval-augmented consolidation",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agent memory architectures that maintain separate episodic (event-trace) and semantic (assertion) stores and route writes between them via retrieval-augmented consolidation. Does not apply to systems that perform single-store append-only logging without promotion, nor to systems where contradiction resolution is deferred entirely to query time.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-avoid-promoting-episodic-traces-into-semantic-memory-during-retrieval-augmented-consolidation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-avoid-promoting-episodic-traces-into-semantic-memory-during-retrieval-augmented-consolidation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-avoid-promoting-episodic-traces-into-semantic-memory-during-retrieval-augmented-consolidation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1572,
    "python_slice_tokens": 376,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is this: **retrieval similarity is not evidence of semantic truth**. Consolidation pipelines typically promote an episodic trace to a semantic assertion when (a) the trace is retrieved repeatedly, or (b) the trace is retrieved as supporting context for a query whose answer it \"matches.\" Both signals are contaminated by retrieval mech...",
    "what_was_observed": "In a consolidation pipeline routing episodic traces to a semantic store, a class of traces began promoting at high rate. The traces were short, entity-dense statements (\"service X runs on port Y\", \"user Z prefers format W\") that scored high on embedding similarity against a broad band of incoming queries because they shared named entities with almost everything. Retrieval counts climbed monotonically, the promotion t...",
    "condition_of_validity": "The promotion rule is valid only when all of the following hold: 1. **Provenance closure.** The episodic trace carries a complete provenance chain (source, timestamp, session, and the query that surfaced it). Traces missing any element are ineligible regardless of retrieval count. 2. **Entailment, not similarity.** A verifier confirms the trace entails the c...",
    "decision_boundary": "The boundary is between **\"retrieved and consistent\"** and **\"entailed and superseding.\"** The former is a routing signal; the latter is a promotion license. Operationally: - If entailment holds, provenance is closed, and no conflict exists → promote. - If entailment holds but a conflict exists → resolve by timestamp and supersession; promote only the winner...",
    "operational_effect": "Enforcing this boundary converts the semantic store from a frequency-weighted cache of retrieved text into a provenance-anchored assertion set. The measurable effects are: promotion rate drops sharply for entity-hub traces; contradiction-resolution rate rises because conflicts are detected against episodic candidates rather than masked by already-promoted as..."
  },
  "matched_failure_symptoms": [
    "OOM_KILL_OR_MEMORY_EXHAUSTION"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "fda47effdf775ab7d6fead1c99b7622c095eb0e5b548f199193e804977f89816",
    "verified_classes": [
      "PromotionInvariantError",
      "EpisodicTrace",
      "SemanticAssertion"
    ],
    "verified_functions": [
      "_provenance_closed",
      "_independent_retrievals",
      "_is_hub_artifact",
      "_entails",
      "route_promotion",
      "_shares_entity"
    ],
    "verified_functions_count": 6,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "PromotionInvariantError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
