explicit-identity

Ensure correct data attribution in distributed systems by passing explicit session IDs and trace IDs to spawned processes, preventing race conditions and misattribution across asynchronous boundaries instead of relying on stale current context.

Pass session IDs to spawned processes by explicitly providing the `--session-id` argument and storing relevant identifiers in state files, ensuring asynchronous operations correctly correlate data and events with the ongoing human-facing session.

Explicit identity maintenance across asynchronous boundaries is the practice of passing unique identifiers like session IDs and span IDs directly between processes, preventing data corruption and ensuring correct correlation in distributed systems without relying on current context.

You need to pass explicit trace IDs in distributed systems when spawning new processes or asynchronous operations, ensuring analysis results and events are correctly associated with their originating session to prevent data misattribution.

Yes, relying on potentially stale current context for process communication causes data corruption and race conditions. Explicitly passing unique identifiers like session IDs ensures robust process communication and accurate state management across boundaries.