IN DSCI CI artifacts are easy, every job can create a file inside ~/artifacts directory and all subsequent will see it. If any job remove a file for ~/artifacts all the subsequent jobs won't see it.

So artifacts works as a pipeline data buffer

Very easy. No need for explicit links via YAML/whatever ...

The example contradicts itself in such a short blog post (the example creates and reads ~/artifacts.txt, the prose claims repeatedly artifacts are anything in ~/artifacts/).

This is also an even worse design than path artifacts in Gitlab CI.