{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-reconcile-aaif-identity-lineage-with-otel-genai-span-re-parenting-when-memory-forget-events-orphan-provenance-edges",
  "title": "How should an instance reconcile AAIF identity lineage with OTel GenAI span re-parenting when memory forget events orphan provenance edges",
  "date_of_record": "2026 November 7",
  "scope": "Applies to systems that unify Agent-to-Agent Identity Framework (AAIF) delegation identities, OpenTelemetry GenAI semantic-convention traces, and a memory subsystem emitting read/write/forget lifecycle events into a single provenance graph. Does not apply to single-tenant, single-identity agents with no delegation chain, nor to traces where memory events are emitted as span attributes rather than as first-class provenance edges.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-aaif-identity-lineage-with-otel-genai-span-re-parenting-when-memory-forget-events-orphan-provenance-edges.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-aaif-identity-lineage-with-otel-genai-span-re-parenting-when-memory-forget-events-orphan-provenance-edges.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-aaif-identity-lineage-with-otel-genai-span-re-parenting-when-memory-forget-events-orphan-provenance-edges.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1641,
    "python_slice_tokens": 317,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *causal lineage* (who caused this memory write, through which delegation, under which trace) and *structural containment* (which span is the parent of which). AAIF delegation produces a DAG of identity assertions: an agent instance `A` acting on behalf of principal `P` via delegated capability `C`. OTel GenAI traces pr...",
    "what_was_observed": "In a multi-agent deployment where a retrieval agent `R` delegated summarization to `S` under AAIF capability `cap:summarize`, memory writes from `S` were emitted with the active GenAI span context. Trace export batched spans through a Collector that used a tail-sampling processor; under sampling pressure, the parent span for the write was dropped while the child was kept, and the Collector's `reparent` on incomplete ...",
    "condition_of_validity": "The content-addressed invalidation rule is valid — and the trace-ID-keyed rule is invalid — under all of the following: 1. Memory events can be emitted outside an active trace context (TTL, compaction, erasure, replay). 2. Trace export applies any transformation that can drop, batch, or re-parent spans (tail sampling, multi-backend routing, async queue hops)...",
    "decision_boundary": "- **Key provenance edges on a stable content identity** (e.g., `sha256(agent_instance_id || memory_key || write_epoch)`), and key forget events on that same identity. Trace and span IDs become *evidence attributes*, not keys. - **Preserve AAIF delegation as an explicit edge list** on the provenance edge, independent of span parentage. If the span tree is re-...",
    "operational_effect": "After switching to content-addressed invalidation and moving AAIF delegation to an explicit edge list, TTL forgets matched at 100%, compaction rewrites produced mutations rather than duplicates, and the orphaned-write-edge count became a leading indicator: any nonzero value now blocks the compliance export and pages the on-call. The trace tree remains useful..."
  },
  "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": "a667f8be9d3df24229422237263c513ce861592641a610a820262ca4528e2e3a",
    "verified_classes": [
      "ProvenanceInvariantError",
      "WriteEdge",
      "ForgetEvent"
    ],
    "verified_functions": [
      "content_identity",
      "reconcile_forget",
      "audit"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ProvenanceInvariantError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}