[ docs ] Built-in menu hierarchy

[flynntsang]

User Story: As a visitor reading the Eidolon docs, I want a logical structure to the index so I can better understand the project on first-read, and can quickly get to relevant pages when I get hands-on.

Suggestions (for discussion)

Think through logical hierarchy of components, likely with two top level bits: agents and agent machines. Ie, in the vein of...

Built-in Components

• AgentResource
  • Agents
  • Agent Processing Unit (APU)
  • LLM Unit
  • LLM Model
  • Logic Unit <-- Agent Tool ???
  • (keep list, e.g., API, Audio, etc)
  • MachineResource
  • File Memory Base
  • Similarity Memory
  • Symbolic Memory
  • ...

Notice agentResource and MachineResource as top level concepts, we can then choose what we want to display in the breakouts

Security and Auth should be present as part of Machine resource, either on sidebar or navigable form spec

[flynntsang]

@LukeLalor I'm thinking about building out the docs further. In my noodling, I think the "built-in" section should actually be called something like "Component Specs" or "Built-in Specifications". Let me know what you think before this gets picked up.