explicit-identity

To prevent race conditions across process boundaries, you must enforce explicit passing of unique identifiers, such as full UUIDs, through function calls and process spawns. This ensures correct data correlation instead of relying on implicit current state.

Asynchronous tasks get misattributed to the wrong session ID when relying on implicit latest states. If the current context changes between task initiation and execution, explicitly passing the original session ID maintains correct association.

Manage trace IDs and session IDs in distributed systems by maintaining distinct ID types for different concepts like root span and turn span. Strictly pass these full UUIDs explicitly across all asynchronous boundaries to ensure robust state management.

You need explicit identity passing for state management whenever data crosses asynchronous or multi-process boundaries. It is required to prevent data corruption and misattribution caused by the current context changing during execution.

Relying on implicit current context in multi-process environments limits you to non-concurrent operations. If a new process starts before an older one finishes, the latest context overwrites the previous state, causing data corruption and lost trace correlation.