The case for user-defined (customised) Junctions
The ArchiMate 3.1 specification currently supports two types of junction: AND and OR. Unlike Elements and Relationships, the specification does not include Junctions in the list of entities that can be extended via stereotyping and tools tend to not display the names of junctions, stereotyped using guillemets or not.
To overcome this restriction, I would like to propose a third type of Junction: CUSTOM whose meaning can be user-defined (via the existing documentation field). Visually, the CustomJunction name should be displayed and the fill colour should be open to the modeller's choice.
Below are a couple of examples where the CustomJunction would be useful in practice.
The fragment on the left expresses the definition of Strong Authentication as being a combination of at least two distinct factors of type "Something you Have", "Something you Are" or "Something you Know".
The fragment on the right models uncertainty, or conditional probability of A being TRUE given that X & Y are in known states.
The suggestion would be 100% backwards compatible and a rather elegant means of expressing non-trivial combinations.