For my first agent, I’m designing a trading assistant for forex and, eventually, stocks. I’ve mapped the initial file ecosystem in Miro before writing the individual files. The entry point is Agent.md, which defines the agent’s purpose and workflow. It links to Soul.md, which describes my preferences and decision-making style and serves as the central directory for: - Goals: objectives and measures of success. - Rules: shared risk limits and market-specific rules. - Configuration: enabled strategies, instruments and trading periods. - Knowledge: market analysis, strategies, economic news and reference material. - Skills: tasks such as analysing markets, running backtests and evaluating risk. - Tools: connections to trading platforms and data sources. - Memory: observations, trading results and lessons learned. I’m taking an ITIL-inspired approach: clear responsibilities, controlled changes, traceable decisions and continual improvement. The intention is for the agent to propose and test improvements before applying them, while keeping risk limits separate from its learning process. This is an architecture sketch, not a working or proven trading system. I’ll start with historical testing and a demo account, building one part at a time. My biggest takeaway so far: a useful file ecosystem is about giving each piece of information a clear home—not creating as many files as possible. How have you separated knowledge, rules and memory in your own agent projects?