Confusing about the workflow context with fork task

[NguyenThiHanhVi-future-aavn]

During using the sdk-java I see the confusion of the workflow context when run the fork task
Here is my workflow dsl
parallelEnrichment: input: from: ${ $context.order } fork: compete: true branches: - pricingEnrichment: input: from: ${ . } set: subtotal: ${ .amount } tax: 20.00 total: ${ .amount + 20.00 } output: as: '${ $input + { "pricing": $output } }' export: as: '${ { "pricing": $output } }' - customerEnrichment: input: from: ${ .customer } set: loyaltyTier: "gold" discountPct: 5 output: as: '${ $input + { "profile": $output } }' export: as: '${ { "customer": $output } }' - riskAssessment: input: from: ${ . } set: riskScore: 12 riskBand: "low" output: as: '${ $input + { "risk": $output } }' export: as: '${ { "risk": $output } }'

1. with compete false
   The workflow output is the combined output from all branches but context is not, it is always the context from last updated branch not the combined context from all branches?
2. with compete flag true
   When first complete branch completed and trigger complete to fork task (state COMPLETED) then the other branch get FAULTED, is fork task status be influented by the failed result or still keep COMPLETED?
3. also with compete flag true
   The workflow output and context sometimes get from different branch like the log below
   [io.serverlessworkflow.impl.BlockingExample.main()] INFO io.serverlessworkflow.impl.BlockingExample - Workflow context: { "pricing" : { "pricing" : { "subtotal" : null, "tax" : 20.0, "total" : 20.0 } } } [io.serverlessworkflow.impl.BlockingExample.main()] INFO io.serverlessworkflow.impl.BlockingExample - Final output: { "profile" : { "loyaltyTier" : "gold", "discountPct" : 5 } }
   I expect the output and the context should be get from the branch winner who completed first. But the test shows output comes from first completed branch and context comes from last updated branch?
   Please help to confirm what should I follow.
   Thanks for your support.

[fjtirado]

These are really good points, unfortunately I'm not sure they really belong here (at least for now, see below)
The compete, according to the spec, only applies to the workflow model.
The context is a shared global variable that is updated independently of the task being executed. That means that, when updated within a fork, you cannot really predict which will be the outcome.
I think these questions belong to the spec, not to the implementation. It should be clarified there first.
Same applies to the task status. Although in that case, yes, maybe we should act differently depending on the compete flag (if a branch won, you can consider that the overall task is successful regardless the result of the other branches), but I feel is also a question on the spec forum.
Can you formulate the question there?
Im closing this here for now.