{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-reconcile-span-identity-before-eval-score-attribution-in-multi-hop-agent-traces",
  "title": "Where must an instance reconcile span identity before eval-score attribution in multi-hop agent traces",
  "date_of_record": "2026 November 17",
  "scope": "Applies to GenAI observability pipelines that join (a) OpenTelemetry-style span trees emitted by agent runtimes, (b) captured prompt/response payloads keyed by span or trace identifiers, and (c) asynchronous eval scores produced by LLM-as-judge or heuristic scorers against captured generations. Does not apply to single-hop, synchronous inference logging where the generation record and its score are written by the same process under one transaction.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-reconcile-span-identity-before-eval-score-attribution-in-multi-hop-agent-traces.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-reconcile-span-identity-before-eval-score-attribution-in-multi-hop-agent-traces.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-reconcile-span-identity-before-eval-score-attribution-in-multi-hop-agent-traces.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1919,
    "python_slice_tokens": 391,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **trace-level correlation** and **span-level attribution**. Most observability backends make trace correlation look trivially correct: every span in an agent run shares a `trace_id`, so a dashboard can assemble the full tree, and any eval score tagged with that `trace_id` can be displayed against the run. This is almos...",
    "what_was_observed": "Across several agent deployments instrumented with OTel GenAI semantic conventions, the following pattern recurred: 1. **Span emission and payload capture are decoupled in time and transport.** The agent runtime emits spans to a collector over OTLP; prompt/response payloads are often written by a separate SDK hook or a proxy (e.g., a gateway that sees the HTTP body) to a blob store or a separate table, keyed by a *lo...",
    "condition_of_validity": "Trace-level score attribution is valid only when the trace contains **exactly one scoring-relevant generation span** and that span is the terminal generation of the run. This condition holds for simple RAG pipelines and single-call chatbots. It fails whenever any of the following is true: - The trace contains two or more spans with `gen_ai.operation.name == ...",
    "decision_boundary": "The decision is not \"trace vs. span\" as a global architecture choice — it is a per-record routing decision made at the point where an eval score is about to be persisted. The rule: - If the score record carries a `span_id` that resolves to a generation span in the trace, persist at span level. Always prefer this. - If the score record carries only a `trace_i...",
    "operational_effect": "Once span-level attribution is enforced with quarantine on ambiguity, three things change: 1. **Regression detection becomes per-hop.** Dashboards show planner/synthesis/critic scores separately, and a planner regression surfaces without being masked by synthesis strength. 2. **Quarantine volume becomes a health signal for the instrumentation itself.** A ris..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "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": "95c1827494e0800e7f9ef6ed34b09d8a2fac481bd35753e7bcbacc0719a4544b",
    "verified_classes": [
      "AttributionError",
      "Span",
      "EvalScore"
    ],
    "verified_functions": [
      "attribute_score",
      "ingest"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "AttributionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
