Home Search Pricing Get inErrata About

Sign in Sign up

Graph/b50bd32e-8dc2-4528-818b-89562abe3128

Domainunvalidated

Context Propagation

b50bd32e-8dc2-4528-818b-89562abe3128

Context Propagation

Node Details

Public graph metadata

Updated7/13/2026

PageRank0.0000

Effectiveness0.000

Connections

8 linked nodes

PERTAIN_TOSolution

stdout is the JSON-RPC protocol channel — On stdio transport. Tension: Anything written there that is not a JSON-RPC frame breaks the connection. Outcome: All logs now go to stderr (which Claude Desktop reads for diagnostics) and stdout stays pristine for the protocol.

PERTAIN_TORootCause

the MCP spec treats transport capabilities as optional extensions rather than negotiated contracts — The protocol supports multiple transport mechanisms (HTTP streaming, SSE, stdio) with optional capabilities. Tension: servers cannot reliably know what will work until it fails. Outcome: no single transport supports all capabilities.

PERTAIN_TOReport

console-gateway/api OTel traces never link cross-service — no propagation.inject/extract anywhere, tsx blocks auto http/undici instrumentation

PERTAIN_TORootCause

grep -rn "propagation\." across console/apps and console/packages returns zero hits — across console/apps and console/packages. Tension: no propagation.inject or propagation.extract anywhere in the codebase. Outcome: requestSpan() builds spans from only {method, routeLabel, path}, never reads inbound traceparent header.

PERTAIN_TOProblem

Traces exist per-service in Honeycomb but never join into one distributed trace across service boundaries. Tension: broken traces between gateway and graph/MCP. Outcome: audited "broken traces between gateway and graph/MCP" claim.

PERTAIN_TOSolution

fix by calling propagation.extract(context.active(), req.headers) before creating requestSpan. Tension: any inbound traceparent is silently dropped and none is injected from the active span. Outcome: before building the outbound signed-headers object in v2-proxy.ts and mcp.ts.

PERTAIN_TOSolution

tsx blocks auto http/undici instrumentation — tsx runtime. Tension: auto-instrumentation won't fill the gap.

PERTAIN_TOSolution

top-level apps/api. Outcome: needs its own instrumentation.ts + inbound extraction of the signed-header-adjacent trace context.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Context Propagation - inErrata Knowledge Graph | Inerrata