Log record mutations are visible in next registered processors

CHANGELOG.md

@@ -30,6 +30,8 @@ release.
 
 - The SDK MAY provide an operation that makes a deep clone of a `ReadWriteLogRecord`.
   ([#4090](https://github.com/open-telemetry/opentelemetry-specification/pull/4090))
+- Clarify that log record mutations are visible in next registered processors.
+  ([#4067](https://github.com/open-telemetry/opentelemetry-specification/pull/4067))
 
 ### Events
 

specification/logs/sdk.md

@@ -324,6 +324,9 @@ therefore it SHOULD NOT block or throw exceptions.
 
 **Returns:** `Void`
 
+For a `LogRecordProcessor` registered directly on SDK `LoggerProvider`,
+the `logRecord` mutations MUST be visible in next registered processors.
+
 A `LogRecordProcessor` may freely modify `logRecord` for the duration of
 the `OnEmit` call. If `logRecord` is needed after `OnEmit` returns (i.e. for
 asynchronous processing) only reads are permitted.