T20-MAS Web App Specification (Conceptual, Stand-alone)
1. Introduction
This document outlines the conceptual specification for a stand-alone, no-backend T20-MAS (Task-Oriented Multi-Agent System) Web Application...
2. Overall Goal
Generation of a specification of a stand-alone T20-MAS Web App, no backend, purely conceptual.
3. Architectural Context and Insights
- Client-Side Execution: All MAS logic, communication, and state management must reside within the browser's JavaScript environment...
- No Backend: Eliminates server-side persistence, APIs, and computation...
- MAS in the Browser: Requires browser-compatible implementations for components like the
MessageBus...
- Conceptual Focus: The specification defines the structure and interfaces without requiring a full implementation...
4. Core Components and Interfaces
4.1. Agent Definition (runtime/agent.py basis)
Agent Class: The fundamental unit of the MAS. Responsible for executing tasks based on its profile (name, role, goal) and system instructions.
4.2. Core Runtime (runtime/core.py basis)
ExecutionContext: Manages the state and context for a workflow, including plans and artifacts...
8. Scope and Limitations
- Conceptual: This specification is conceptual and does not include implementation details for browser-specific adaptations.
- Stand-alone: No backend server is involved; all processing occurs client-side.
- Limited Scalability: Performance and memory are constrained by the user's browser capabilities.
- No Data Sharing: Each user session is independent; data is not shared between users.
DeepSite - 🧬
Remix
