Today, we have a propagation context on every span that receives a random traceId and spanId (unless it is continued from an external service). We use these IDs to populate trace headers for further propagation.

A scope always has a propagation context, and you can't really tell if this is a "random" one or one that is continued from somewhere...

We should maybe reconsider this, as today this leads to a bunch of confusion, and may lead to cases where we send a parent_span_id that does not exist (because it comes from the propagationContext, not an actual span).