From 2399f5763f6b6ee4ad957596fe1eafb3bb335ea0 Mon Sep 17 00:00:00 2001
From: Pratik Mankawde <3397372+pratikmankawde@users.noreply.github.com>
Date: Tue, 8 Sep 2026 14:42:32 +0100
Subject: [PATCH] docs(telemetry): name the consensus trace strategy value
 "random"

The plan doc offered `"attribute"` as the alternative to `"deterministic"`
for consensus_trace_strategy. The parser accepts `"random"`; "attribute"
described the correlation mechanism rather than the setting's value. Note
also that the alternative is experimental and not used.
---
 OpenTelemetryPlan/06-implementation-phases.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/OpenTelemetryPlan/06-implementation-phases.md b/OpenTelemetryPlan/06-implementation-phases.md
index cf1e58f779..c7fc9af1e2 100644
--- a/OpenTelemetryPlan/06-implementation-phases.md
+++ b/OpenTelemetryPlan/06-implementation-phases.md
@@ -178,7 +178,8 @@ Phase 4a (establish-phase gap fill & cross-node correlation) will add:
 
 - **Deterministic trace ID** derived from `previousLedger.id()` so all validators
   in the same round share the same `trace_id` (switchable via
-  `consensus_trace_strategy` config: `"deterministic"` or `"attribute"`).
+  `consensus_trace_strategy` config: `"deterministic"`, or `"random"` which is
+  experimental and not used).
   See [Configuration Reference](./05-configuration-reference.md) for full
   configuration options.
 - **Round lifecycle spans**: `consensus.round` with round-to-round span links.