[ feature ] Documentation that matches the YAML spec would be helpful for beginners learning your platform.

[mafudge]

User Story

• As a new user to your platform
• I want to read your documentation
• So that I can easily translate your spec into the required YAML format.

I've been fiddling with your platform most of the day. It is pretty cool. One frustrating aspect of learning it is the "guessing" of where the parts in the documentation belong in the yaml spec.

Some kind of complete spec, showing how everything is configured manually would go a long way towards understand the platform. While the opinionated approach is useful to get started, it makes it challenging to advance beyond the basics /demos, and I feel this hurts adoption.

[flynntsang]

Thanks for writing this up! I hope you're enjoying working with Eidolon. I'm adding a few notes here for when we go through the prioritization review.

I think we have three types of configuration files: machine, agent, and reference. We have a docs section named "Builtin Components" that is generated directly from the code. It includes machine and a flattened list of agent properties.

We should consider at least one level of hierarchy below Agent, e.g.:

Machine

• Symbolic Memory
• Similarity Memory
• File Memory

Agents

• APUs
• LLM Providers
• Tools

@mafudge you might find this helpful as you progress: https://www.eidolonai.com/ide_help . We also have a number of documentation issues pending here: Eidolon Open Source (view) . Thanks again for taking the time to submit this issue!