#diagramming strategies
earnest gust
Disclosure: I'm really into diagrams of all types. Don't hesitate to ask me to back down.
OK, so IME, at this stage of development, people want to see diagrams that:
- describe the causal relationship between elements
- describe the sequence of events within a process.
So, something like C4 can illustrate the two contexts (dagger control and data planes) and then within each are the containers (eg. host, OCI, SDK...)
Something like a sequence diagram can illustrate the commands, the caching, I/O to network and storage.
In fact, @vale moth does something similar in https://chainloop.dev/blog/software-supply-chain-attestation-easy-way#see-it-in-action
I suspect that there are tools which can read the Golang AST and make cool diagrams (similar to the venerable PlantUML https://plantuml-documentation.readthedocs.io/en/latest/diagrams/sequence.html)