docs: add tdd about snark artifacts management and distribution solution

[sripwoud]

This document stemmed from discussions I had with @cedoor while working on refactoring how snark artifacts are managed/fetched in zk-kit (see privacy-scaling-explorations/zk-kit#240)

See #1

[sripwoud]

@cedoor @AtHeartEngineer tagging you first here, hoping you can share this in your circles with people who might need/be interested in this.

[cedoor]

@artwyman tagging you here as this started from a private discussion we had a few weeks ago. Your input would be very appreciated. I imagine this work will be very useful for Zupass as well.

[cedoor]

Looks great!

[sripwoud]

@NicoSerranoP @glamperd Does this make sense to you? This repo focuses more on the distribution of artifacts that are the outcome of trusted setups (p0tion's scope). Still there might be some overlap...

[NicoSerranoP]

I love this idea ❤️! It could be directly integrated to p0tion's output. One challenge I see in trying to automate the ceremony + publishing is that in case the team has a lot of versions/bugs then it might take a lot of bandwidth and space. The npm maintainers will be at the mercy of third party teams running ceremonies with p0tion.

We should think in a filtering mechanism :)

[glamperd]

Yes, automation is feasible. We can then think about how best to establish the full chain of trust - from github code to all the artifacts.