LMOS: Quickstart a dev experience env

[RJ111111]

As an external person who wants to experience LMOS , i need to have an environment quickly up and running on my local with all LMOS components and all requires services following minimal set of instructions.

Success metric:
An LMOS agentic environment is up and running on my local with two agents, one sample API already integrated for agent, and with some observability tools and services also pre-integrated. This setup should up and ready within five minutes following minimal set of instructions.

Description:

Acceptance Criteria:

1. Instructions must be clear enough so that a semi-technical person is also able to setup the environment and experience an agent using LMOS. This implies instruction or reference to instructions for obtaining an API key or setting up and installing docker should also be included in the guide.
2. Upon readiness, urls to access the following must be clearly shared in the terminal console, as well as must also be mentioned in the Quickstart documentation:

• Url to access an Observability tool
• Url to access a sample agent pre-integrated in the Quickstart.
• Url to access a Logging and Monitoring tool.
• Url to access an Arc agent builder module.
• Url to Quickstart documentation.

3. When the system is ready, i should be able to interact with a generic pre-defined agent, and also able to use the associated observability and monitoring tools.

Dependencies:

1. Access to LLM via some API key.

Assumptions:

[kaikreuzer]

I have a couple of comments on this:

• I would claim that we had this in place with the very initial lmos-demo already. But this proved to be too inflexible as those two pre-installed agents might not be the use case that people are interested in. We therefore decided to make the demo a bit more modular: 1. Install LMOS itself + 2. Choose a sample use-case and install it. Both steps require only a single call of an "install.sh" script, i.e. they are as simple as it can get.
• If the current demo setup isn't easliy working for people, we have to figure out the reasons. Clearly, documentation can always be made more attractive. But maybe there are also problems with memory + cpu requirements that might be too much for an average developer PC. Maybe there are other issues that we will need to find out.
• A question that we imho will have to address is how people can start playing around with the demo setup after installation. How to adjust the prompts? How to add a new agent that has been built with Arc? Etc pp.