A repository to rule all repositories

Probably a bad title..

As a beginner in this eco-system this project currently has 160 repositories. As you can imagine that is a bit overwhelming for someone coming in new.

I've read the specifications and have a good idea of the lay of the land as it relates to the different components. What I don't have a good understanding is the implementation of those various components in the eco system as a whole.

Could I suggest creating a repository that is maybe something as simple as General Implementation, where it encompasses all the steps to:

1) Bring up a DID services, with a local driver ?
3) Bring up a Web Node service, that provides a protected method hello-world
2) Create a DID for Bob
3) Create a DID for Alice
4) Request the hello-world method/resource from Alice to Bob
5) Authorize
6) Receive resource from from Bob
7) Display resource

A project that contains maybe docker images for all of this would be great along with a test that implements it.

I know the project not might be there right now, but if we could agree on the steps that would be a minimal viable eco-system I think it would be helpful not only to set a goal, but for new comers coming in that want to get up to speed.

If there is already something like this can you point me into the direction, sorry for posting here, but I really had no where to go to get a lay of the land from an implementation perspective as a whole.

I would be happy to put the docker compose together, and the test script that would exercise all these services and learn along the way.

Cheers,
Marty

No files or existing tests are named. Start by mapping the repositories and components needed for the listed DID and Web Node flow, then check whether an end-to-end example already exists. Done would be a documented minimal ecosystem with Docker-based setup and a test script exercising the complete request, authorization, and resource flow.

Written by the indexing model from the issue text.