The work of this epic covers the description of the problem, findings, and recommended changes described in https://rchain.atlassian.net/wiki/spaces/CORE/pages/732790805/listenForDataAtName.
Basically there are 3 separate topics that need to be addressed to make the platform accessible to users:
dag discovery (ability to build a representation of the dag and deploys in it)
deployment introspection (ability to track data in a given deploy)
block discovery (ability to track the lifecycle of a deploy in blocks)
Arguably point 1 and 3 are the same but there was concern voiced that an immediate api for users interested in a singular deploy is a good feature.
The difference between 1 and 3 is:
1 is focused on the global state of all blocks and their deploys
3 is focused on tracking a particular deploy
It seems that a more robust solution will be achieved with 1 & 2.
3 can be delivered as a nice-to-have.