14 KiB
14 KiB
tags:: #todoist-task, PROJECTS/MOSAICO , meeting date:: 01-07-2025 - 09:25 progress:: {{renderer :todomaster}}
- ### Tasks
collapsed:: true
- {{query (and [[TODO]] [[Missione ROMA Mosaico]] )}}
query-sort-by:: block
query-table:: true
query-sort-desc:: false
query-properties:: [:block]
- ### Notes
- Agenda: 
- Participants: 
- **First day of meeting [[01-07-2025]]**
query-table:: true
query-properties:: [:block]
collapsed:: true
- ### Overview
collapsed:: true
- 
- ### WP1 Presentation
collapsed:: true
- 
- 
- 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.
- 
- 
- This is the API of the server that is executing agents
- {:height 480, :width 951}
- TODO Look at Phoenix technology
- TODO [[p2]] WP2 and WP3 need to decide where to put the telemetry function
- 
- 
- 
- {:height 561, :width 951}
- 
- TODO Vedere LangFuse for observability.
- 
- 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.
- 
- 
- TODO [[p1]] Da guardare A2A agent card per la tassonomia relativa al repository
- 
- 
- 
- TODO [[p2]] 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
- 
- 
- 
- TODO This is an idea related to the WP2 taxonomy
- 
- ### WP2 Presentation
collapsed:: true
- 
- TODO Developer Interface is not the right naming. THis needs to be changed
- 
- TODO LiteLLM can be seen as a possible alternative for the telemetry
- 
- 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 [[p1]] 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 [[p2]] Link the taxonomy with the SEBOK
- TODO Investigate also the support of "contracts".
- We are talking about different and disgributed systems, we should have some contracts capabilities among them
- How do you agree on them?
- This also involves the concepts of monitoring. What about if agents to not respect the contracts.
- ### WP3 Presentation
collapsed:: true
- 
- 
- Tipically used for developing agents in a rule-based manner
- How people thinks!
- 
- 
- 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 !?
- 
- 
- 
- 
- 
- This scenario comes from the interaction with Collins
-
- ### WP4 Presentation
collapsed:: true
- 
- 
- ... different profiles (from WP2)
- 
- 
- 
- {:height 532, :width 921}
- 
- 
- 
-
- 
- 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.
- 
- 
- 
- **Second day of the meeting [[02-07-2025]]**
collapsed:: true
- ### WP10 Presentation
collapsed:: true
- [Florence Bonnet | CEPR](https://cepr.org/about/people/florence-bonnet)
- 
- 
- 
- 
- IMM can be classified as controller under the terminology of GDPR. This needs to be clarified.
- 
- Also in this case there are potential issues violating GDPR
- Are we profiling users?
- 
- In this case there might be some AI Act concerns.
- 
- 
- More detailed technical assessment at use case level
- The system is considered as high risk! not only for its functionalities but also for the use cases
- 
- GPAI - General Purpose AI systems
- 
- 
- 
- {:height 572, :width 980}
- 
- 
- 
- 
- 
- 
- 
- 
- This table is meant for the controller.
- 
- This would be only for use case providers that will implement their solution. This needs to be done only if we will play the role of "Controller".
- She mentioned also *Global DPIA*
- Risk assessment
- Risky use of data
- ### WP6 Presentation
collapsed:: true
- 
- 
- 
- 
- 
- 
- 
- This is related to Task 6.1
- 
- Not yet contents on YouTube (real project video will be released later)
- We removed X from our socialmedia. We should decide what to do. It makes sense to increase the Linkedin KPI
- So far no visits to schools or alike
- {:height 582, :width 980}
- TODO [[p1]] Aggiungere presentazione MOSAICO a FSE
- 
- 
- Concerning T6.1 and T6.3 (from Eclipse)
- {:height 512, :width 921}
- We are at the preparation phase
- 
- 
- 
- TODO In september we will a first internal development workshop. Who is going there?
- 
- We expect to have a panel on AI and someone from MOSAICO is expected to go there!
- Concerning Task 6.4 (Netcompany)
- 
- 
- The survey aims at collecting how partners intent to exploit the results
- 
- four pillars
- 
- 
- 
- {:height 549, :width 980}
- 
- The "contributing partners" column should be "Exploitation partners"
- 
- 
- 
- TODO We have now a latex template for deliverables. It's in our Sharepoint. DOwnload it!
-
- ### WP5 Presentation
collapsed:: true
- 
- 
- 
- 
- 
- 
- 
- 
- 
-
- ### WP8 and WP9
collapsed:: true
- Talked about deliverable 8.2
- 
- 
- ### Discussion
- TODO [[p2]] Look at [MOSAICO Architecture - Google Drawings](https://docs.google.com/drawings/d/1zyO2GLFj8PtQD9j6MZ1AksQwwLM_XmZX8AOPGNs8m_Y/edit)
- **Third day of the meeting [[03-07-2025]]**
- Agenda: [MOSAICO 2nd Co-Creation meeting Rome_proposed agenda_20250619.docx](https://imtatlantiquefr.sharepoint.com/:w:/r/sites/MOSAICO/_layouts/15/Doc.aspx?sourcedoc=%7BBC69EB4B-582A-4E6B-A86A-13D04EF8FA93%7D&file=MOSAICO%202nd%20Co-Creation%20meeting%20Rome_proposed%20agenda_20250619.docx&action=default&mobileredirect=true)
- Link: https://gov.teams.microsoft.us/l/meetup-join/19%3agcch%3ameeting_cb5648e689bb4db19ab298cdfad07f3f%40thread.v2/0?context=%7b%22Tid%22%3a%227a18110d-ef9b-4274-acef-e62ab0fe28ed%22%2c%22Oid%22%3a%2272d155af-f561-43e3-88f0-0ae9416888e8%22%7d
- NBG Use Case
- {:height 516, :width 830}
- 
- 
- #critical How all of this is related to orchestration! Scripts need to be developed by solution agents. WHo develop that?
- 
- #critical
- 
- It is importa nt to stress that agents will be developed by use case partners!!!!#important
-