Signal Boundary Event should start child execution?

Camunda 7 Topics Discussion & Questions
1

In this process
Signal
I would expect the non-interrupting signal catch boundary event to execute in a new child execution of T2.

ProcessInstance[4]
    ConcurrentExecution[7] in UserTask_1
    ConcurrentExecution[8]
        ScopeExecution[11] in UserTask_2
        - Variable 'var' = val
        - EventSubscription[12] for Signal_1 in BoundaryEvent_1ed7ldr

ProcessInstance[4]
    ConcurrentExecution[18] in UserTask_3
    ConcurrentExecution[8]
        ScopeExecution[11] in UserTask_2
        - Variable 'var' = val
        - EventSubscription[12] for Signal_1 in BoundaryEvent_1ed7ldr

I expected execution 18 to be a child of execution 11. Why is that not the case?

UnitTest: GitHub - apinske/camunda-engine-unittest at signal

2