yes, that’s also been visualized in the docs. The feature you’re are references between multiple projects, since you can trigger jobs in a different repository to continue, if you do not follow the monorepo approach. Adding these triggers and references can get complex - this is where a better visualization helps customers.
Portions of the trigger keyword have been moved to Core for parent/child pipeline support recently. That is why the downstream pipeline above works for you as well. This was made happen to not overly complicate things, and adds a nice feature for everyone.