{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-of-the-genai-trace-correlation-id-be-minted-to-survive-memory-mutation-and-where-does-late-minting-silently-break-the-invariant",
  "title": "Where must an instance of the GenAI trace correlation ID be minted to survive memory mutation, and where does late-minting silently break the invariant?",
  "date_of_record": "2026 November 12",
  "scope": "Applies to any GenAI system that emits a single trace correlation ID (hereafter `trace_id`) intended to bind a prompt, its retrieval fan-out, its tool calls, and any memory-mutation side effects into one causally ordered record. Does *not* apply to single-turn stateless inference with no retrieval, no tools, and no persistent memory, where a request-scoped ID is sufficient.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-of-the-genai-trace-correlation-id-be-minted-to-survive-memory-mutation-and-where-does-late-minting-silently-break-the-invariant.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-the-genai-trace-correlation-id-be-minted-to-survive-memory-mutation-and-where-does-late-minting-silently-break-the-invariant.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-the-genai-trace-correlation-id-be-minted-to-survive-memory-mutation-and-where-does-late-minting-silently-break-the-invariant.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1703,
    "python_slice_tokens": 361,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **request-scoped correlation** and **causality-scoped correlation**. A request-scoped ID is minted at the HTTP/gRPC ingress boundary and is adequate when the trace is a flat request→response span. A causality-scoped ID must be minted *before the first mutation of shared state that the trace is supposed to explain* — i....",
    "what_was_observed": "In a multi-turn agent with a long-term memory store, the following sequence was observed during a post-incident reconstruction: 1. Turn N: model issues a `memory.write` tool call to persist a user preference. The ingress-minted `trace_id` is propagated in the tool-call envelope. 2. The memory service accepts the write, but enqueues it to an async applier queue. The applier worker **does not receive the `trace_id`** —...",
    "condition_of_validity": "The invariant \"every memory mutation is causally attributable to exactly one `trace_id`\" holds only under all of the following: - The `trace_id` is present in the **mutation payload itself**, not merely in the transport envelope. Envelope propagation is lost at every async boundary (queues, retry workers, batch compactors, outbox pattern dispatchers). - The ...",
    "decision_boundary": "Mint the `trace_id` at ingress **only if** all mutation paths are synchronous and in-process. The moment any of the following is true, the `trace_id` must be minted *earlier* — at the turn/session coordinator, before the first retrieval or tool dispatch — and must be **carried in the payload of every mutation**, with the mutation store rejecting payloads tha...",
    "operational_effect": "Concretely, the operational consequence is that incident reconstruction of a poisoned or corrupted memory entry changes from an O(1) trace lookup to an O(n) table scan with timestamp heuristics that are unreliable across retry and clock skew. The failure is silent under normal operation (traces look complete because tool servers echo the ID) and surfaces onl..."
  },
  "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": "d94987f7e6558dae580c794b263eb2bebef6bafad8bed23ac6252d2430c63259",
    "verified_classes": [
      "UnattributedMutationError",
      "MutationRecord"
    ],
    "verified_functions": [
      "apply_mutation",
      "compact_memory",
      "__init__"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "UnattributedMutationError"
    ],
    "sample_fail_closed_invariants": [
      "compaction run has no originating trace_id; rewritten entries would be orphans"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}