tags:: #todoist-task, [[PROJECTS/MOSAICO]] date:: [[01-07-2025]] - 09:25 progress:: {{renderer :todomaster}} - ### Tasks - - ### Notes - Agenda: ![MOSAICO Consortium meeting Rome_proposed agenda_202506165408279409830273888.pdf](../assets/MOSAICO_Consortium_meeting_Rome_proposed_agenda_202506165408279409830273888_1751381413979_0.pdf) - Participants: ![MOSAICO 2nd Consortium meeting_Rome_list of participants_202506238683233499270025632.pdf](../assets/MOSAICO_2nd_Consortium_meeting_Rome_list_of_participants_202506238683233499270025632_1751381740630_0.pdf) - ### Todos collapsed:: true - {{query (and [[TODO]] [[Missione ROMA Mosaico]])}} query-table:: true query-properties:: [:block] - **First day of meeting [[01-07-2025]]** collapsed:: true - ### Overview collapsed:: true - ![image.png](../assets/image_1751354765576_0.png) - ### WP1 presentation collapsed:: true - ![image.png](../assets/image_1751355881307_0.png) - ![image.png](../assets/image_1751356317096_0.png) - Where is the consensus agent? - The shown workflow is an initial simplification. The idea is having more complex workflows where consensus agents are part of the workflow. - ![image.png](../assets/image_1751356391471_0.png) - ![image.png](../assets/image_1751356495836_0.png) - This is the API of the server that is executing agents - ![image.png](../assets/image_1751357021426_0.png){:height 480, :width 951} - TODO Look at Phoenix technology - TODO WP2 and WP3 need to decide where to put the telemetry function - ![image.png](../assets/image_1751358801620_0.png) - ![image.png](../assets/image_1751359025611_0.png) - ![image.png](../assets/image_1751359581584_0.png) - ![image.png](../assets/image_1751359775463_0.png){:height 561, :width 951} - ![image.png](../assets/image_1751359960093_0.png) - TODO Vedere LangFuse for observability. - ![image.png](../assets/image_1751360262806_0.png) - You can see different calls / tools used - Compare to Phoenix, the license is more friendly and you can use this completely locally. - Opentelemetry is a communication protocol and LangFuse supports this protocol. - ![image.png](../assets/image_1751360448322_0.png) - ![image.png](../assets/image_1751360766405_0.png) - TODO Da guardare A2A agent card per la tassonomia relativa al repository - ![image.png](../assets/image_1751361032317_0.png) - ![image.png](../assets/image_1751361131943_0.png) - ![image.png](../assets/image_1751361170015_0.png) - TODO The agent discovery mechanism is very much related to that of MOSAICO. Have a look at them especially to see what is the taxonomy underpinning them - ![image.png](../assets/image_1751361461752_0.png) - ![image.png](../assets/image_1751361630543_0.png) - ![image.png](../assets/image_1751361681318_0.png) - TODO This is an idea related to the WP2 taxonomy - ![image.png](../assets/image_1751361765405_0.png) - ### WP2 presentation collapsed:: true - ![image.png](../assets/image_1751363781466_0.png) - TODO Developer Interface is not the right naming. THis needs to be changed - ![image.png](../assets/image_1751364615575_0.png) - TODO LiteLLM can be seen as a possible alternative for the telemetry - ![image.png](../assets/image_1751364754080_0.png) - TODO How do they implement guard rails? - This is for security but also **reliability** - TODO How scalable are they in terms of agents? - TODO Do they support agents in different technologies? - TODO What about parallel executions? - TODO Improve the relation vs existing model repositories - TODO Have a look at the different repositories shared by Antonio - https://beeai.dev/agents - https://www.agentlocker.ai/ - https://aiagentslist.com/ - [Taxonomy of AI Agent Skills - Agntcy](https://docs.agntcy.org/oasf/taxonomy/) - TODO Look at Traces and Metrics (OpenTelemetry with Spring) - Our application should be ready to gather telemetry - It is related to LangFuse - Traces to LangFuse - Metrics go to Graphana - OpenTelemetry does both - We talk metrics but we should also talk about the evaluator - TODO Check alternative technologies than MongoDB - https://docs.spring.io/spring-ai/reference/api/vectordbs.html#_vectorstore_implementations - TODO Link the taxonomy with the SEBOK - - - ### WP3 Presentation collapsed:: true - ![image.png](../assets/image_1751373339095_0.png) - ![image.png](../assets/image_1751373489739_0.png) - Tipically used for developing agents in a rule-based manner - How people thinks! - ![image.png](../assets/image_1751373575932_0.png) - ![image.png](../assets/image_1751373666549_0.png) - How to make BDI more pervasive in MOSAICO - (last point and see next slide) - WE can select an agent with respect to "desires" typically writte in natural language - Believes for selecting agents - Agent will expose intentions while it's adoption (e.g. in vscode you can accept or not what agent is going to do) - WP3 is kind of requiremnt for WP1 !? - ![image.png](../assets/image_1751373946026_0.png) - ![image.png](../assets/image_1751374070429_0.png) - ![image.png](../assets/image_1751374209613_0.png) - ![image.png](../assets/image_1751374443438_0.png) - ![image.png](../assets/image_1751374491508_0.png) - This scenario comes from the interaction with Collins - - ### WP4 Presentation - ![image.png](../assets/image_1751380184004_0.png) - ![image.png](../assets/image_1751380295091_0.png) - ... different profiles (from WP2) - ![image.png](../assets/image_1751380541463_0.png) - ![image.png](../assets/image_1751380591305_0.png) - ![image.png](../assets/image_1751381052161_0.png) - ![image.png](../assets/image_1751381117177_0.png){:height 532, :width 921} - ![image.png](../assets/image_1751381195013_0.png) - ![image.png](../assets/image_1751381211852_0.png) - ![image.png](../assets/image_1751381248184_0.png) - - ![image.png](../assets/image_1751381592398_0.png) - Attributes of the Agent class are related to the repository. For instance, the confidence of each agent should be available from the repo. - The list of attributes of the Agent class should be refined by considering also who is going to value/compute them. - ![image.png](../assets/image_1751382098076_0.png) - ![image.png](../assets/image_1751382272258_0.png) - ![image.png](../assets/image_1751382349242_0.png)