Start locally

STANDARD · Profile revision 1

W3C Trace Context

A W3C Recommendation defining interoperable HTTP trace-context propagation through traceparent and tracestate headers.

standardw3cdistributed-tracingcorrelation

Why it is in the map

It is the foundational cross-vendor correlation standard, and its narrow scope prevents propagation from being mistaken for trace content or reconstruction sufficiency.

Tracevity boundary

A documented field can support reconstruction, but its presence alone does not prove completeness, authenticity, authorization, or external settlement.

Profile findings

What the documentation can—and cannot—establish

Each row distinguishes source evidence from Tracevity's bounded interpretation. “Not documented” describes the reviewed sources; it does not prove an implementation cannot record the artifact.

01

System identity

Partially documented

Distributed trace and parent correlation identifiers are documented.

Tracevity interpretation

These identifiers correlate operations but do not identify a product, runtime, agent definition, agent instance, session, or principal.

Limit

Agent-specific identity requires another semantic layer.

Primary evidence (1)
02

Principal and delegation

Not documented

Principal and delegation evidence is outside the standard.

Tracevity interpretation

A trace ID must not be treated as actor identity or delegated authority.

Limit

Identity and authorization records require separate correlated systems.

Primary evidence (1)
03

Instruction and context

Not documented

Instruction and application context semantics are not defined.

Tracevity interpretation

Correlation headers establish no reconstruction content beyond propagation context.

Limit

Application payloads or semantic conventions must supply all instruction and context evidence.

Primary evidence (1)
04

Decision artifacts

Not documented

Decision artifacts are outside the standard.

Tracevity interpretation

None may be inferred from trace identifiers or parentage.

Limit

A separate application-level trace schema is required.

Primary evidence (1)
05

Model activity

Not documented

Model activity is outside the standard.

Tracevity interpretation

A correlated request cannot establish that a model call was recorded.

Limit

Model evidence requires another semantic convention or trace source.

Primary evidence (1)
06

Tool and MCP activity

Not documented

Tool and MCP activity semantics are outside the standard.

Tracevity interpretation

Trace context can connect tool spans only when another source defines and emits those spans.

Limit

Propagation support does not guarantee that a downstream component preserves or records tool semantics.

Primary evidence (1)
07

Effects

Not documented

External effects are outside the standard.

Tracevity interpretation

Trace propagation proves no provider acceptance or state change.

Limit

Effect verification requires destination evidence.

Primary evidence (1)
08

Human control

Not documented

Human-control evidence is outside the standard.

Tracevity interpretation

None may be inferred from trace correlation fields.

Limit

Approval and intervention systems require separate correlation.

Primary evidence (1)
09

Outcome

Not documented

Outcome evidence is outside the standard.

Tracevity interpretation

A propagated trace ID establishes no execution or business outcome.

Limit

Outcome semantics require application telemetry and external evidence.

Primary evidence (1)
10

Trace integrity

Not documented

Trace correlation is documented, but record integrity is not.

Tracevity interpretation

A trace ID is not origin authentication or custody evidence.

Limit

Timestamp and clock provenance are also outside the standard.

Primary evidence (1)
11

Portability

Documented

Cross-vendor trace-context portability is the standard's primary documented capability.

Tracevity interpretation

This is context propagation portability, not trace-payload or semantic portability.

Limit

No export file, import destination, conversion, or semantic-loss model is defined.

Primary evidence (1)
12

Privacy

Partially documented

A narrow privacy prohibition for trace-context header values is documented.

Tracevity interpretation

The prohibition does not control sensitive content elsewhere in a trace or application payload.

Limit

Retention, deletion, redaction, hashing, and customer-controlled capture are outside the standard.

Primary evidence (1)

Reconstruction reading

Do not collapse these findings into one score.

This profile describes documented evidence surfaces. Whether they are sufficient depends on the reconstruction question and the other identity, authorization, tool, and destination records available.

Potentially useful evidence

  • Identity: Distributed trace and parent correlation identifiers are documented.
  • Portability: Cross-vendor trace-context portability is the standard's primary documented capability.
  • Privacy: A narrow privacy prohibition for trace-context header values is documented.

Explicit gaps or uncertainty

  • Principal: Identity and authorization records require separate correlated systems.
  • Context: Application payloads or semantic conventions must supply all instruction and context evidence.
  • Decisions: A separate application-level trace schema is required.
  • Models: Model evidence requires another semantic convention or trace source.
  • Tools: Propagation support does not guarantee that a downstream component preserves or records tool semantics.

Source register

1 reviewed primary sources

  1. Trace ContextW3C Distributed Tracing Working Group · STANDARD SPECIFICATION · observed August 28, 2026 · current
    Open source ↗

Next question

What evidence does your use case require?

Move from documented field presence to an explicit reconstruction target, or examine selected directional format mappings without changing this system's documentation posture.

Trace Reconstruction Requirements Explore compatibility evidence