Determine the homotopy type that captures intended concurrent-process behavior

Determine whether the homotopy type of directed path spaces or the homotopy type of trace spaces, in which changes of speed and waiting time are declared unobservable, better captures the intended behavior of concurrent processes.

Background

The paper constructs a saturated directed space whose directed path space and trace space have different weak homotopy types: the trace space is a square and therefore contractible, while the directed path space has a nontrivial fundamental group. This demonstrates that quotienting directed paths by reparametrizations can discard homotopical information.

The authors point out that this discrepancy creates an unresolved modeling question for applications in computer science. Directed paths retain distinctions involving changes of speed and waiting time, whereas traces identify such changes as unobservable. The paper does not determine which of these two homotopy types more accurately represents the intended behavior of concurrent processes.

References

For applications to computer science, this raises the question of which homotopy type captures the intended behavior: that of directed paths or that of traces, in which changes of speed and waiting time are declared unobservable?

The homotopy types of directed path and trace spaces  (2609.11454 - Gaucher, 10 Sep 2026) in Section 1, Introduction, immediately following Theorem 1.1 (page 2)