copycat82 Gate Problems:
... neither dynamic, nor proper ...

copycat82 commits plagiarism, and it is worse than trivial, in general, as also spellable about its macro-gate problems.

copycat82: volatility, although without versatility
too tricky to manage, whether to model-with, or to verify

copycat82's input macros, turn out to be neither dynamic, nor proper. Because they neglect data, they cannot adapt themselves (over time), although because of the un-proper (=volatile) Petri net implementations, three of the five, may change their response, at any pass.

Some quasi-static copycat82 "logic" macros may fluctuate, at any pass. e.g: The "priority" becomes undeterministic, after the first pass through the higher priority path. Strange, it is. (See the inputs "xor" and "or", too.)

The problems of any such contagious input/output macro, stand to contaminate their containers, too - without warning!

SARA static/reduceable vs. E-nets dynamic/versatile

The SARA/UCLA strategy is to provide only a few i/o control logic, and let these be nested, when to specify multiple paths. This is static. It has its advantages, especially because the SARA/UCLA strong-reduction algorithm can compress nets, to improve verifier performance.

By contrast, E-net resolution-procedures, are tools to build new behaviors. These are dynamic, and versatile. For example, an input may favor a location with minimum time-requirement, or if it is visited the least, etc. (i.e: A transition may let a different priority to each path, at each turn - with programmer control.) It is also trivial to implement those static i/o control logic (macros) of SARA, with E-nets.

copycat82 provides no software tools, although E-nets, and SARA, were with their software tools (machine-processable), even when they were published - many years before copycat82. In fact, that was the reason for using predicates. Not to "trace them mentally," but for computers to interpret (run) them.

With macros, NN73 had already extended the primitive two-input E-net transitions to multiple-inputs, as well as present new macros to stand as new types of transitions or locations, e.g: the Q-macro-location, to act as a queue/stack.

The input macro "and" corresponds to the J-transition of E-nets. The other four of the entrance-macros correspond to the Y-transition, or alternatively, they imitate SARA input control logic. Not original, in any case. But the extra problem is their quirkiness.

Further Reading

The plagiarism of copycat82 encompasses its input-gate, and its output-gate, too.

An attempt to imitate JSP primitives? Or, parallelism?