[logseq-plugin-git:commit] 2025-12-27T19:07:25.270Z

This commit is contained in:
2025-12-27 20:08:10 +01:00
parent 1c76754387
commit a578313353
624 changed files with 11511 additions and 4361 deletions
+57 -75
View File
@@ -7,78 +7,60 @@
date:: [[04-07-2025]] - 11:44
duration::
-
- ### Notes sul deliverable D2.1
- Da considerare anche il prompt?
- {{renderer :mermaid_68668a24-ce43-472e-b787-a53b895f7c75, 3}}
collapsed:: true
- ```mermaid
classDiagram
class Agent {
id
name
version
owner
}
class Capability {
domain
taskType
supportedLanguages
inputFormats
outputFormats
}
class PerformanceKPI {
accuracy
latencyMs
resourceConsumption
robustnessMetrics
}
class Governance {
license
dataResidency
GDPRCompliance
auditTrailAvailable
}
class FairnessEthics {
biasDetected
fairnessConstraints
explanationCapabilities
}
class RuntimeEnvironment {
runtime
requiredLibraries
hardwareAcceleration
}
class Provenance {
trainingDataSources
modelLineage
lastUpdated
}
class ContactInfo {
maintainerEmail
documentationUrl
}
class AgentRepository {
<<service>>
}
Agent --> Capability : has
Agent --> PerformanceKPI : provides
Agent --> Governance
Agent --> FairnessEthics
Agent --> RuntimeEnvironment
Agent --> Provenance
Agent --> ContactInfo
AgentRepository --> Agent : manages
```
- Agents should be also marked if they keep information or not for IP purposes.
-
- ### [[Deliverable D2.1]]
- What we're envisioning is that the protocol exposes the information about the agents in a given agent server, which then can be easily consumed by your repository (for indexing). This is the same approach as A2A agent cards and as MCP tool descriptions. A single agent server only lists its own agents: the MOSAICO repository is the one that actually indexes all the agents available across all the servers.
- I think this is needed, because I cannot imagine people going to a web interface and filling in form field after form field with all this information. A2A precisely does this so that they could do a type of web crawler that would go through "well-known URIs" ([http://host/.well-known/agent.json](http://host/.well-known/agent.json)) to find agents at will. In fact, I suspect your repository may need to do exactly this.
- ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAhIg5c2AAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
-
- ### [[MENTORING/TESISTI]]
collapsed:: true
- **Marco Giarrusso**
- **Mariama Celi S. de Oliveira**
- Rehearsal presentation
- what about adding an explanatory workflow to show an orchestration of agents with Dify or AutoGPT?
- Collaborative optimization task--> explain
- Just motivate the choices for the configurations slide 8
- Slide 9
- too small
- Slide 13
- What do you mean with Each pipeline runs only once?
-
- **Motunrayo Ibiyo**
- Rehearsal presentation
collapsed:: true
- Mention MOSAICO at the beginning where we are studying the usage of LLM-based multi agent systems to support software engineering tasks
- Very fast, reduce the content and speak slowly. Too many slides!!! You should cut half of them!!!
- It's easy to get lost in the details
- Slides 4
- What are the limitations of existing approaches?
- Slide 6
- with-out (typo)
- Slide 7
- Put the updated reference
- Slide 8
- highlight the different components while presenting (one by one)
- Slide 10
- ![image.png](../assets/image_1752844038326_0.png)
- what does it mean?
- Slide 11
- Many typos
- a file in the package is...
- Slide 12
- ![image.png](../assets/image_1752844166908_0.png)
- too many things
- Slide 14
- ![image.png](../assets/image_1752844268908_0.png)
- It's too much,
- It's more beneficial presenting some explanatory examples instead of all these numbers, in line with what you have with slide 16.
-
- TOOLS evaluated
- Qualitative + Quantitative
- AutoGen
- AutoGPT
- Dify
- SemanticKernel
- LlamaIndex
- Heystack
- Qualitative
- Those from Motunrayoi
-