MyLife-Services
diff --git a/‎README.md
Lines changed: 1 addition & 1 deletion b/‎README.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎inc/js/agents/system/README.md
Lines changed: 6 additions & 2 deletions b/‎inc/js/agents/system/README.md
Lines changed: 6 additions & 2 deletions
diff --git a/‎inc/js/agents/system/asset-assistant.mjs renamed to ‎inc/js/agents/system/asset-agent.mjs
Lines changed: 13 additions & 11 deletions b/‎inc/js/agents/system/asset-assistant.mjs renamed to ‎inc/js/agents/system/asset-agent.mjs
Lines changed: 13 additions & 11 deletions
@@ -164,7 +164,7 @@ MyLife itself is an open-source project and, aside from LLM technologies at the
 
 3. **Bot Functionality and Intelligence Management**
    - The application features a sophisticated bot system, capable of creating and managing different types of bots like personal assistants, biographers, health bots, etc.
-   - OpenAI's GPT-3 model is integrated for generating responses and interacting with users through bots, as observed in the `class-avatar-functions.mjs` and `mylife-agent-factory.mjs` files.
+   - OpenAI's GPT-3 model is integrated for generating responses and interacting with users through bots, as observed in the `mylife-avatar.mjs` and `mylife-factory.mjs` files.
 
 4. **Session Management**
    - Managed through the `MylifeMemberSession` class, handling user sessions, consents, and alerts.
 
@@ -2,12 +2,16 @@
 
 The MyLife system incorporates a suite of specialized assistants, each designed to augment various aspects of the avatars within the platform. These assistants follow consistent coding protocols and are currently intended exclusively for integration with avatars, enhancing their functionality and interactivity.
 
-- **Asset-Assistant (File Handler)**: This assistant manages file-related operations, ensuring efficient handling, storage, and retrieval of files within the system. It acts as a central hub for file management tasks, streamlining the process of dealing with various file formats and data types.
+- **Asset-Agent**: (File Handler) This agent manages file-related operations, ensuring efficient handling, storage, and retrieval of files within the system. It acts as a central hub for file management tasks, streamlining the process of dealing with various file formats and data types.
 
-- **Evolution-Assistant**: Central to the avatar's developmental journey, the Evolution Assistant orchestrates the growth and maturation of avatars. It guides avatars through different phases of evolution, from creation to retirement, tailoring the development process according to the avatar's specific needs and contexts.
+- **Bot-Agent**: (Bot Handler) One of the most fundamental agents available, represents an object that manages the menagerie of Bots allocated to the current member's team. Also manages Teams.
+
+- **Collections-Agent**: (Lists Handler) This agent manages collections for mass operations.
 
 - **DOM-Assistant**: The Document Object Model (DOM) Assistant is pivotal in managing and manipulating the structure of data and documents within the system. It plays a key role in ensuring the data is organized and accessible in a way that is both efficient and intuitive.
 
+- **Evolution-Assistant**: Central to the avatar's developmental journey, the Evolution Assistant orchestrates the growth and maturation of avatars. It guides avatars through different phases of evolution, from creation to retirement, tailoring the development process according to the avatar's specific needs and contexts.
+
 - **Preferences-Assistant**: This assistant is dedicated to personalizing user experiences by managing and adapting to user preferences. It ensures that avatars can cater to individual tastes and requirements, making interactions more tailored and relevant.
 
 - **Settings-Assistant**: Focused on configuration management, the Settings Assistant allows for the customization and adjustment of system settings. This ensures that avatars can operate within the parameters that best suit the user's needs and the system's operational environment.
 
@@ -1,29 +1,31 @@
 //	imports
 import fs from 'fs'
 import mime from 'mime-types'
-import FormData from 'form-data'
-import axios from 'axios'
 //	module constants
-const { MYLIFE_EMBEDDING_SERVER_BEARER_TOKEN, MYLIFE_EMBEDDING_SERVER_FILESIZE_LIMIT, MYLIFE_EMBEDDING_SERVER_FILESIZE_LIMIT_ADMIN, MYLIFE_SERVER_MBR_ID: mylifeMbrId, } = process.env
-const bearerToken = MYLIFE_EMBEDDING_SERVER_BEARER_TOKEN
+const {
+	MYLIFE_EMBEDDING_SERVER_BEARER_TOKEN: bearerToken,
+	MYLIFE_EMBEDDING_SERVER_FILESIZE_LIMIT,
+	MYLIFE_EMBEDDING_SERVER_FILESIZE_LIMIT_ADMIN,
+	MYLIFE_SERVER_MBR_ID: mylifeMbrId,
+} = process.env
 const fileSizeLimit = parseInt(MYLIFE_EMBEDDING_SERVER_FILESIZE_LIMIT) || 1048576
 const fileSizeLimitAdmin = parseInt(MYLIFE_EMBEDDING_SERVER_FILESIZE_LIMIT_ADMIN) || 10485760
-class oAIAssetAssistant {
+class AssetAgent {
 	#globals
 	#llm
 	#mbr_id
 	#response
 	#vectorstoreId
 	#vectorstoreFileList=[] // openai vectorstore versions
-	constructor(mbr_id, globals, llm){
-		this.#mbr_id = mbr_id
-		this.#globals = globals
+	constructor(factory, llm){
+		this.#mbr_id = factory.mbr_id
+		this.#globals = factory.globals
 		this.#llm = llm
 	}
 	/**
 	 * Initializes the asset assistant by uploading the files to the vectorstore.
 	 * @param {string} vectorstoreId - The vectorstore id to upload the files into, if already exists (avatar would know).
-	 * @returns {Promise<oAIAssetAssistant>} - The initialized asset assistant instance.
+	 * @returns {Promise<AssetAgent>} - The initialized asset assistant instance.
 	 */
 	async init(vectorstoreId){
 		if(!vectorstoreId?.length)
@@ -143,5 +145,5 @@ class oAIAssetAssistant {
 			throw new Error(`Unsupported media type: ${ mimetype }. File type not allowed.`)
 	}
 }
-// exports
-export default oAIAssetAssistant
+/* exports */
+export default AssetAgent