Spaces:
Build error
Build error
Merge branch 'main' of https://huggingface.co/spaces/Agents-MCP-Hackathon/TheAgora
Browse files
README.md
CHANGED
|
@@ -1,3 +1,16 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
# The Agora: Where artificial minds gather to forge wisdom
|
| 2 |
|
| 3 |
### TRACK : mcp-server-track
|
|
@@ -41,10 +54,18 @@ Facilitates structured dialogues and 'debates' between AI models, allowing them
|
|
| 41 |
|
| 42 |
Here's a conceptual workflow:
|
| 43 |
|
| 44 |
-
|
|
|
|
|
|
|
|
|
|
| 45 |
|
| 46 |
- *User Problem Submission (Gradio UI):*
|
| 47 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 48 |
IMAGE
|
| 49 |
|
| 50 |
A user submits a complex problem or query via the Gradio web interface. The input is typically a natural language prompt, potentially with accompanying data.
|
|
@@ -54,6 +75,10 @@ Image Description:
|
|
| 54 |
|
| 55 |
A screenshot of a Gradio interface with an input text box for the user's problem and a "Submit" button.
|
| 56 |
|
|
|
|
|
|
|
|
|
|
|
|
|
| 57 |
- *Problem Parsing & Initial Distribution (MCP Orchestrator):*
|
| 58 |
|
| 59 |
- *The MCP Orchestrator (a custom backend server) receives the user's problem.*
|
|
@@ -63,25 +88,26 @@ A screenshot of a Gradio interface with an input text box for the user's problem
|
|
| 63 |
Based on pre-defined roles, the orchestrator dispatches the problem to specific models or groups of models for initial analysis and proposals. For instance, Claude might get an ethical framing, GPT a creative angle, and Mistral a technical breakdown.
|
| 64 |
|
| 65 |
|
| 66 |
-
|
|
|
|
|
|
|
|
|
|
| 67 |
|
| 68 |
-
Individual Model Reasoning & Proposals
|
| 69 |
|
| 70 |
-
Each designated AI model processes the problem based on its specialty
|
| 71 |
|
| 72 |
-
Models generate their initial solutions, ethical considerations, technical analyses, or creative approaches
|
| 73 |
|
| 74 |
-
These individual outputs (including their 'reasoning' and 'confidence scores' if applicable) are sent back to the MCP Orchestrator
|
| 75 |
|
| 76 |
|
| 77 |
-
Image Description: Multiple thought bubbles or document icons, each representing a different AI model's unique output and reasoning.
|
| 78 |
|
| 79 |
-
Debate Orchestration (MCP Orchestrator):
|
| 80 |
|
| 81 |
The orchestrator initiates a multi-turn 'debate' or 'review' phase.
|
| 82 |
|
| 83 |
- *Round 1 (Initial Review): Each model's proposal is shared (anonymously or attributed) with other relevant models.*
|
| 84 |
-
|
| 85 |
- *Round 2 (Rebuttal & Refinement): Models respond to critiques, refine their initial proposals, or adjust their positions.*
|
| 86 |
|
| 87 |
Image Description: A visual representation of AI models exchanging arguments, possibly with arrows indicating flow of information and feedback loops.
|
|
@@ -107,10 +133,13 @@ Result Presentation (Gradio UI):
|
|
| 107 |
|
| 108 |
- *Gradio renders this information to the user in a clear, structured, and interactive format.*
|
| 109 |
|
|
|
|
|
|
|
| 110 |
|
| 111 |
-
|
| 112 |
|
| 113 |
|
|
|
|
| 114 |
|
| 115 |
## π οΈ Technologies Used
|
| 116 |
Frontend: Gradio (for interactive web interface)
|
|
@@ -161,9 +190,5 @@ python app.py
|
|
| 161 |
## π€ Contributing
|
| 162 |
|
| 163 |
Aditya Katkar\
|
| 164 |
-
Github\
|
| 165 |
-
LinkedIn
|
| 166 |
-
|
| 167 |
-
|
| 168 |
-
## π License
|
| 169 |
-
(Information about the project's license will be placed here.)
|
|
|
|
| 1 |
+
---
|
| 2 |
+
title: The Agora
|
| 3 |
+
emoji: π
|
| 4 |
+
colorFrom: red
|
| 5 |
+
colorTo: blue
|
| 6 |
+
sdk: gradio
|
| 7 |
+
sdk_version: 5.33.0
|
| 8 |
+
app_file: app.py
|
| 9 |
+
pinned: true
|
| 10 |
+
license: mit
|
| 11 |
+
short_description: Where artificial minds gather to forge wisdom
|
| 12 |
+
---
|
| 13 |
+
|
| 14 |
# The Agora: Where artificial minds gather to forge wisdom
|
| 15 |
|
| 16 |
### TRACK : mcp-server-track
|
|
|
|
| 54 |
|
| 55 |
Here's a conceptual workflow:
|
| 56 |
|
| 57 |
+
|
| 58 |
+

|
| 59 |
+
|
| 60 |
+
|
| 61 |
|
| 62 |
- *User Problem Submission (Gradio UI):*
|
| 63 |
|
| 64 |
+

|
| 65 |
+
|
| 66 |
+
|
| 67 |
+

|
| 68 |
+
|
| 69 |
IMAGE
|
| 70 |
|
| 71 |
A user submits a complex problem or query via the Gradio web interface. The input is typically a natural language prompt, potentially with accompanying data.
|
|
|
|
| 75 |
|
| 76 |
A screenshot of a Gradio interface with an input text box for the user's problem and a "Submit" button.
|
| 77 |
|
| 78 |
+
|
| 79 |
+

|
| 80 |
+
|
| 81 |
+
|
| 82 |
- *Problem Parsing & Initial Distribution (MCP Orchestrator):*
|
| 83 |
|
| 84 |
- *The MCP Orchestrator (a custom backend server) receives the user's problem.*
|
|
|
|
| 88 |
Based on pre-defined roles, the orchestrator dispatches the problem to specific models or groups of models for initial analysis and proposals. For instance, Claude might get an ethical framing, GPT a creative angle, and Mistral a technical breakdown.
|
| 89 |
|
| 90 |
|
| 91 |
+
- *A diagram showing the MCP Orchestrator sending the problem to multiple distinct AI models.*
|
| 92 |
+
|
| 93 |
+
|
| 94 |
+

|
| 95 |
|
| 96 |
+
- *Individual Model Reasoning & Proposals:*
|
| 97 |
|
| 98 |
+
- *Each designated AI model processes the problem based on its specialty.*
|
| 99 |
|
| 100 |
+
- *Models generate their initial solutions, ethical considerations, technical analyses, or creative approaches.*
|
| 101 |
|
| 102 |
+
- *These individual outputs (including their 'reasoning' and 'confidence scores' if applicable) are sent back to the MCP Orchestrator.*
|
| 103 |
|
| 104 |
|
|
|
|
| 105 |
|
| 106 |
+
Debate Orchestration (MCP Orchestrator): Everything happens at backend and Final winner response is displayed in frontend
|
| 107 |
|
| 108 |
The orchestrator initiates a multi-turn 'debate' or 'review' phase.
|
| 109 |
|
| 110 |
- *Round 1 (Initial Review): Each model's proposal is shared (anonymously or attributed) with other relevant models.*
|
|
|
|
| 111 |
- *Round 2 (Rebuttal & Refinement): Models respond to critiques, refine their initial proposals, or adjust their positions.*
|
| 112 |
|
| 113 |
Image Description: A visual representation of AI models exchanging arguments, possibly with arrows indicating flow of information and feedback loops.
|
|
|
|
| 133 |
|
| 134 |
- *Gradio renders this information to the user in a clear, structured, and interactive format.*
|
| 135 |
|
| 136 |
+
- *A Gradio output screen showing a structured summary of the AI council's deliberation and the final consensus.*
|
| 137 |
+
|
| 138 |
|
| 139 |
+

|
| 140 |
|
| 141 |
|
| 142 |
+

|
| 143 |
|
| 144 |
## π οΈ Technologies Used
|
| 145 |
Frontend: Gradio (for interactive web interface)
|
|
|
|
| 190 |
## π€ Contributing
|
| 191 |
|
| 192 |
Aditya Katkar\
|
| 193 |
+
[Github](https://github.com/Addyk-24)\
|
| 194 |
+
[LinkedIn](https://www.linkedin.com/in/aditya-katkar-673930340)
|
|
|
|
|
|
|
|
|
|
|
|