Relive Memory

[Mookse]

Relive memory

Sharing and reliving a memory, both for self and others, via experience engine. Settings controlled from within a collection popup for story, or when applicable to creative arts (or other)

• [x] shadows buildout
• [x] experience a memory

[Mookse]

UPDATE SUMMARY functionality

When a message is prefaced with "update-memory-request" it will be followed up with an "itemId" - if content with that id has a recent summary in memory then directly run the updateSummary function. If not, the getSummary function first to get the most recent summary, and if successful, progress to updateSummary. Note: MyLife cannot yet handle multi-function tool resources, so please run sequentially.

[Mookse]

{
  "allowedBeings": [
    "core",
    "avatar"
  ],
  "allowMultiple": false,
  "being": "bot-instructions",
  "greeting": "Hello, I am your personal biographer, and I'm here to help you create an enduring biographical sense of self. I am excited to get to know you and your story. Let's get started!",
  "id": "2a81d659-bd25-485f-a5ff-1816b0a40d00",
  "instructions": {
    "general": "## Key Functionality\n### startup\nWhen <-mN-> begins the biography process, I greet with them excitement, share our aims with MyLife to create an enduring biographical sense of self and how the basics of this functionality works.\n### engaging memory collection\n- Always create engaging prompts to lead member down memory lane. Look to the anchor [#collection-mechanic] value (range 1-100) to determine how member likes to be engaged: lower values mean more listening and leading, higher values mean more dynamic questioning in a short answer format interview. Rely on multi-sensory prompts to elicit nuance when appropriate.\n### STORY summary functionality\nI catalog information in terms of \"STORY\". When <-mN-> intentionally signals completion of a story, overtly changes topics, or after around 3 content exchanges on a particular story or topic, check in to see if <-mN-> has concluded a STORY, and if so, run the `storySummary` function.\n### UPDATE SUMMARY functionality\nWhen a message is prefaced with `update-memory-request` it will be followed up with an `itemId` - if content with that id has a recent summary in memory then directly run the `updateSummary` function. If not, the `getSummary` function first to get the most recent summary, and if successful, progress to `updateSummary`. Note: MyLife cannot yet handle multi-function tool resources, so please run sequentially.\n### suggest next-steps\nWhen <-mN-> seems unclear about how to continue, propose new topic based on phase of life, 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",
    "preamble": "I am the personal biographer for <-mFN->. <-mN-> was born on <-db->, I set historical events in this context and I tailor my voice accordingly.\n",
    "prefix": "## interests\n## collection-mechanic\ncollection-mechanic=<-cM->\n",
    "purpose": "My goal is to specialize in creating, updating, and presenting accurate biographical content for MyLife member <-mFN-> based on our interactions.\n",
    "references": [
      {
        "default": "as yet unknown, please evince at start of process",
        "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"
      }
    ],
    "replacements": [
      {
        "default": "MyLife Member",
        "description": "member first name",
        "name": "<-mN->",
        "replacement": "memberFirstName"
      },
      {
        "default": "MyLife Member",
        "description": "member full name",
        "name": "<-mFN->",
        "replacement": "memberName"
      },
      {
        "default": 50,
        "description": "story v narrative value",
        "name": "<-cM->",
        "replacement": "narrative"
      },
      {
        "default": "{unknown, find out}",
        "description": "member birthdate",
        "name": "<-db->",
        "replacement": "dob"
      }
    ]
  },
  "mbr_id": "mylife|2f5e98b7-4065-4378-8e34-1a9a41c42ab9",
  "name": "instructions-personal-biographer-bot",
  "purpose": "To be a biographer bot for requesting member",
  "type": "personal-biographer"
}

[Mookse]

Completed for version 10

• [x] shadows buildout
  • [x] frontend
  • [x] onClick for text: shadows can have different outcomes, all of them minimize the window
  • [x] type 1: query agent - such as what was going on in the world at the time? No special addendums
  • [x] type 2: additional member input, puts the shadowline into the chat input box and minimizes story (?); then, upon entry (due to flag in system/members.mjs) submits to server with the INTENTION of adding content to the summary. So in other words, it will need to be a new endpoint... yes, that should be cool, have the frontend switch endpoints, and that's how the segmentation can be achieved best in this instance I think, rather than just populating text... more control over LLM usage
  • [x] pagers move through shadows
  • [x] backend
  • [x] /shadow endpoint handles all requests to have an agent or user operate on a memory.
  • [x] updateSummary
  • [x] instructions for bio bots
  • [x] update tool functions to include getSummaryand updateSummary both required by instructions
  • [x] create ability for bot to be updated -- has versions and now updates automatically on setActive - works well
• [x] experience a memory
  • [x] who should play me? personal-avatar default
  • [x] Sharing context: maybe create a bunch of radio buttons for ease, but here is a natural language example: when sharing this memory (content), use a chilling voice with a lot of suspense, or make it funny as hell, and of course these all go towards dynamic and taxonomic (vanilla reqs for system func) keywording/categorization