Journal Bot

[Mookse]

Journal Bot

First attempt at something @Mookse would use every day, as narrative capture is not top-of-mind. A companion who can help me keep a journal of interesting ideas or topics on which I'd like to keep my ideas. It's not inwardly focused per se in my personal usage, but I would anticipate it could most certainly support self-examination and introspection. I want it to be able to categorize and recall my ideas on a topic. Should be part of its thread-bearing innate ability, but of course in conjunction with uploads (so make sure it is connected to store) and functions for journal item submission events.

• Create instruction set
  • Azure => mylife (Cosmos) => system.Documents => .rightClick() => "Create Document"
  • hit enter to accept a newly created guid as primary id for new document
  • paste in system id: mylife|2f5e98b7-4065-4378-8e34-1a9a41c42ab9
  • copy and paste most content from most similar bot-type look for a few things in particular to change
    • instructions.replacements, bot-type specific default name (see comment)
    • instructions.purpose, .preamble could use same data, I think these are heritage, preamble preferred
    • instructions.general: where the majority of alteration should go - use markdown script with literal string \n for line breaks
    • note: needed to refresh system.Documents entirely in VSCode.Azure in order to see changes
• createBot endpoint: note: one-time only
  • determine trigger for bot-creation
  • endpoint: _memberRouter.post('/bots/create', createBot)
  • add to avatar bots
  • prune output, which is bot data - { bot_id, bot_name: name, description, id, purpose, type, }
• entrySummary(): associated function similar to biog-bot that submits a journal entry collection item
  • globals.mjs: const mAiJsFunctions add entry definition for new functionality: entrySummary
  • mylife-agent-factory.mjs: in mGetAIFunctions() create type in switch and reference necessary components, here file-search in addition to entrySummary
  • solution requires one-time fix to pipeline in order to consolidate in mGetAIFunctions
  • mylife-llm-services.mjs: add case entrysummary in mRunFunctions()
  • mylife-agent-factory.mjs: add entry()
  • mylife-data-service.js: entry()
• collections updates
  • recall from server as type entry form: journal
  • create frontend collection
• front-end
  • icon and assets
  • "add bot" button to trigger
  • Teams Select placeholder
  • addTeamMember()
• bug: thread id in console did not seem correct

Additionally an attempt to catalog the amount of time it takes to create a MyLife bot realistically, and best practice process for creating the next one ;)

[Mookse]

      {
        "default": "Squinch",
        "description": "journaler name",
        "name": "<-bN->",
        "replacement": "bot_name"
      }