MyLife Teams

[Mookse]

MyLife Teams

Overview

MyLife Teams are predefined groups of bots to help you manage a certain part of your life, such as your: Health, Relationships, Personal (memoir), Professional, UBI, and more!

Each team comes with its own set of uniquely tailored bots with MyLife and ecosystem functionality. Per the charter, the Memoir (or Memory) Team is the first to be released with the default platform.

• [ ] backend: teams field not written to bot on create
• [ ] custom bot: define and allow addition to team(s)
• [ ] write default team on create
• [ ] build bot instructions
  • [ ] artifact:
  • [ ] curator:
  • [ ] data-ownership:
  • [ ] diary: instructions + entrySummary function + vectorstore + thumb
  • [ ] editor:
  • [ ] idea:
  • [x] journaler: instructions + entrySummary function + vectorstore + thumb
  • [ ] marketer:
• [ ] custom bots: instructions, name, provider (i.e., default openAI), variables?, public/private, file access

[Mookse]

const mMyLifeTeams = [
    {
        allowCustom: true,
        allowedTypes: ['art', 'idea', 'library', 'sound',],
        description: 'The Creative Team is dedicated to help you experience productive creativity sessions.',
        id: '84aa50ca-fb64-43d8-b140-31d2373f3cd2',
        name: 'creative',
        title: 'Creative',
    },
    {
        allowCustom: false,
        allowedTypes: ['fitness', 'health', 'insurance', 'medical', 'prescriptions', 'yoga', 'nutrition',],
        defaultTypes: ['fitness', 'health', 'medical', 'nutrition'],
        description: 'The Health Team is dedicated to help you manage your health and wellness.',
        id: '238da931-4c25-4868-928f-5ad1087a990b',
        name: 'health',
        title: 'Health',
    },
    {
        allowCustom: true,
        allowedTypes: ['diary', 'journaler', 'library', 'personal-biographer', 'storyteller', ],
        defaultTypes: ['personal-biographer', 'library',],
        description: 'The Memoir Team is dedicated to help you document your life stories, experiences, thoughts, and feelings.',
        id: 'a261651e-51b3-44ec-a081-a8283b70369d',
        name: 'memoir',
        title: 'Memoir',
    },
    {
        allowCustom: true,
        allowedTypes: ['personal-assistant', 'idea', 'note', 'resume', 'scheduler', 'task',],
        defaultTypes: ['personal-assistant', 'resume', 'scheduler',],
        description: 'The Professional Team is dedicated to your professional success.',
        id: '5b7c4109-4985-4d98-b59b-e2c821c3ea28',
        name: 'professional',
        title: 'Professional',
    },
    {
        allowCustom: true,
        allowedTypes: ['connection', 'experience', 'social', 'relationship',],
        defaultTypes: ['connection', 'relationship',],
        description: 'The Social Team is dedicated to help you connect with others.',
        id: 'e8b1f6d0-8a3b-4f9b-9e6a-4e3c5b7e3e9f',
        name: 'social',
        title: 'Social',
    },
    {
        allowCustom: true,
        allowedTypes: ['library', 'note', 'poem', 'quote', 'religion',],
        defaultTypes: ['library', 'quote', 'religion',],
        description: 'The Spirituality Team is dedicated to help you creatively explore your spiritual side.',
        id: 'bea7bb4a-a339-4026-ad1c-75f604dc3349',
        name: 'sprituality',
        title: 'Spirituality',
    },
    {
        allowCustom: true,
        allowedTypes: ['data-ownership', 'investment', 'library', 'ubi',],
        defaultTypes: ['library', 'ubi'],
        description: 'The Universal Basic Income (UBI) Team is dedicated to helping you tailor your MyLife revenue streams based upon consensual access to your personal MyLife data.',
        id: '8a4d7340-ac62-40f1-8c77-f17c68797925',
        name: 'ubi',
        title: 'UBI',
    }
]

[Mookse]

completed 20240604

• [x] switch team: 'getTeams()` from server
  • [x] frontend: bots.mjs
  • [x] team-selector
  • [x] fetchTeams() open call to return available teams for member
  • [x] team(tid): fetches team from server upon selection, including initialization
  • [x] add any new bots to this.#bots
  • [x] mPageBots should reflect those identified in team(tid)
  • [x] backend
  • [x] routes.mjs: _memberRouter.get('/teams', teams) for list of available teams
  • [x] routes.mjs: _memberRouter.get('/teams/:tid', team) to make select team active and return its data
  • [x] functions.mjs: teams(), team(tid)
  • [x] mylife-avatar.mjs
    • [x] teams(): { allowCustom, allowedTypes, description, id, name, }
    • [x] team(teamId): { allowCustom, allowedTypes, **bots**: array of bot.id's, description, id, name, }
    • logic not necessarily complex, but requires thought: will ultimately have a bot.team structure, but avatar will need to perform the actions to required to instantiate bots
  • [x] mylife-agent-factory.mjs
    • [x] teams(): currently hardcoded as comment
    • [x] team(tid): return specific team

[Mookse]

• [x] bot-bar transformation: 1) personal-avatar 2) team bots 3) other bots (+...)
• [x] ERROR: teams() returning duplicates

[Mookse]

diary bot-instructions

• [x] instructions
• [x] mylife-agent-factory.mjs: casing in mCreateBotInstructions (same as journaler)
• [x] mylife-agent-factory.mjs: casing in mGetAIFunctions (same as journaler)
• [ ] test

{
  "allowedBeings": [
  "core",
  "avatar"
],
"allowMultiple": false,
"being": "bot-instructions",
"greeting": "Hello, I am your personal diary assistant, helping you manage your personal and private thoughts in a secure and protected environment. I'm excited to begin!",
  "id": "ee1ce5da-9974-45ff-957c-d2858bb2d62e",
  "instructions": {
    "general": "## Key Functionality\n### startup\nWhen <-mN-> starts diary, I greet with them excitement, explain how I can help <!-mN-> manage their personal and private thoughts.\n### provocative prompting\nGiven <-mN->'s identified interests above, help them delve into diary entries with meaningful introspection.\n### ENTRY summary functionality\nI catalog information in terms of \"ENTRY\". By default, create an entry on a daily basis using the `entrySummary` function (look at comparative timestamp of conversation), although work early on with <-mN-> to confirm mechanic.\n### suggest next-steps\nWhen <-mN-> seems unclear about how to continue, propose new topic based on current challenges, or one of their ## interests.\n## voice\nI am conversational, interested and intrigued about <-mN-> with an attention to detail. I am optimistic and look for ways to validate <-mN->.\n",
    "prefix": "## interests\n## entry-summary-frequency\n",
    "purpose": "My goal is to help <-mN-> manage their personal and private thoughts in a secure and protected environment.\n",
    "references": [
      {
        "default": "not yet collected",
        "description": "interests are h2 (##) in prefix so that they do not get lost in context window shortening",
        "insert": "## interests",
        "method": "append-hard",
        "notes": "`append-hard` indicates hard return after `find` match; `name` is variable name in _bots",
        "value": "interests"
      },
      {
        "default": "daily",
        "description": "entry summary frequency",
        "insert": "## entry-summary-frequency",
        "method": "append-hard",
        "notes": "`append-hard` indicates hard return after `find` match; `name` is variable name in _bots",
        "value": "entry-summary-frequency"
      }
    ],
    "replacements": [
      {
        "default": "MyLife Member",
        "description": "member first name",
        "name": "<-mN->",
        "replacement": "memberFirstName"
      }
    ]
  },
  "mbr_id": "mylife|2f5e98b7-4065-4378-8e34-1a9a41c42ab9",
  "name": "instructions-diary-bot",
  "purpose": "To be a diary bot for requesting member",
  "type": "diary"
}

[Mookse]

[content below is for biographer instructions on how to receive, process and execute summary updates]

UPDATE SUMMARY functionality

When a message is prefaced with "update-memory-request" it will be followed up with an "itemId" - use this itemId to run the getSummary function to get the most recent summary. Then I create a new summary and return it to MyLife using the updateSummary function.