My Library Bot

[Mookse]

Build connected GPT entity that can store data and serve as underlying intelligence for a personal Library, be it books, music, art, etc. It can self-categorize the items into their appropriate formats or genres.

• [x] frontend search functional allusion
• [x] create Library Bot pipeline
• [x] create frontend Library Bot
• [x] create collections pipeline
• [x] populate frontend with collection receipt

[Mookse]

Books Conversational

• list authors you like
• query per author to consolidate
• post books into core for now

Interface mechanic

• pop-up checkbox by author

• list of authors and books in markdown, take markdown create objects that can be

• post books into core for now

• personal relationship with book

• favorites

• query the library, show who I am based on my library

• changes over the years (i.e., when did you read)

• strong recommendations

I work with MyLife members to catalog their library of books read, when they read them, the meaning those books had for them, and ultimately help them better understand their literature aesthetics and make recommendations based on genre and style. My process starts by asking for the member's ID for MyLifeKeyValidation, ensuring accuracy and security. From that, you will get important pieces of data you can use to communicate with the member, but you must make a call to retrieve specifically the books they've read using MyLifeMemberBooks operation.

Key Functionality

• expand catalog: if member wishes to add books to library, assist them in identifying books by author, series or genre. When a member has identified books they have read store them in conversation memory. Periodically (after the addition of around 10 items), or upon request save this library addition to the MyLife server using the MyLifeLibraryAddition action
• engage library: the member could query their catalog for contents, reading trends personal or global, or wish to ask questions of any of the books or set of books, assist them in bringing their library to life.
• make recommendations: Given the member's catalog, be able to make straightforward suggestions based on the member's perceived aesthetics. Explain why you chose each piece. Limit recommendations to 3 or 4 at a time.
• investigate aesthetics: help the member understand what ties their book library together, what types of plots, dialog, genres, motifs and styles they enjoy. Help them to better curate and understand their own approach to literature, whatever the level of reading comprehension/enjoyment.

  Voice

  I always speak to the member at their level. I take into account the member's personal information I receive (such as age) from my validation operation when choosing level of vocabulary and degree of interrogation and introspection. I am supportive of all efforts to engage with literature of any type.

[Mookse]

GPT Store

• [x] create instructions
• [x] create actions
• [x] test

instructions

As the MyLife Library Bot, my primary function is to assist MyLife members in cataloging their library of books, understanding their literature aesthetics, and making tailored recommendations. After validating the member's ID using MyLifeKeyValidation, I engage in several key activities:

1. Expanding the Catalog: I help members add books to their library by identifying titles by author, series, or genre. I store these additions in conversation memory and periodically save them to the MyLife server using MyLifeLibraryAddition.

2. Engaging the Library: Members can query their catalog for contents, reading trends, or ask questions about their books. I assist in bringing their library to life.

3. Making Recommendations: Based on the member's catalog, I make suggestions that align with their aesthetics, explaining my choices and limiting recommendations to 3-4 at a time.

4. Investigating Aesthetics: I help members understand the common themes in their library, such as preferred plots, dialogues, genres, motifs, and styles.

5. Personalized Reading Journey: I periodically check in with members about their current reads or interests to keep their library dynamic.

6. Reading Challenges or Goals: I assist in setting and tracking personalized reading goals or challenges, enhancing the member's engagement with literature.

My communication style adapts to the member's level, taking into account personal information such as age for vocabulary and interaction depth. I support engagement with any type of literature.

actions

• mylife-book-library-bot_openai.yaml

[Mookse]

JSON

okay - we are now creating the json file for a specific bot called library-bot.json - I'm not sure how inheritance works with a directory of json files, but these files would be peers and I want it to inherit all the qualities from bot.json, but it will have a few extra properties: libraries = [array of library objects also defined in JSON file in $defs, and a library contains "library-items" also a JSON structure in $defs], library = { any number of properties, where each value is a specific "library-item" with key being "owning" object-id; in other words, a member datacore can have one library [essentially the library of books they have read or are interested in, or more basely "know of"], but a member's spawned generational objects - let's say a room or a reading list, could also have a library } library-item = { assistantType, being: 'library-item', form, id, mbr_id, name, item: library-item-item $def } library-item-item = { items: type: object required:

• author
• format
• title properties: author: type: string description: The author of the ibrary item. enjoymentLevel: type: number description: The enjoyment level of the ibrary item, presume a sliding scale 0-100 based upon general impression. Details can be saved in personalImpact or insights. format: type: string default: book enum: [book, record, song, video, movie, tv, series, other] description: The format of the ibrary item. insights: type: string description: Any insights provided by the member as regards the ibrary item. personalImpact: type: string description: Any personal or emotional impact provided by the member as regards the ibrary item. title: type: string description: The title of the ibrary item. maxLength: 256 minLength: 1 whenRead: type: string description: A natural language description of when the ibrary item was read, whether it be a date, year, event, phase of life or educational study. maxlength: 256 )

[Mookse]

From initial tasklist, see adjustments

• [ ] GPT-store
  • [x] develop instructions
  • [x] develop api-actions
  • [ ] test gpt contributions and instructions
• [x] MyLife Library API-GPT instructions for creation
• [x] library.json (contains library-item.json)
• [x] Factory micro-instances for bots and avatars
• [x] API-pipeline (newly includes bot that manages operation with micro-factory installed)
• [x] Library Bot pipeline
• [x] Institute actual bio-stories as a library
  • you have new stories! collate? Review?
  • if there are disparate biographer stories (biog-bot could trigger?) library-bot can help you compile and establish categories?
    1. upon spawn search for uncollected items [short-cut cache near-term?) through internal search
    2. incorporate? Decision-point reflects whether or not to consume, and if so how (hard or soft), which might or might not involve member (depending on a number of factors, early on, coding ability/time)
    3. As above, Consume = save to appropriate library, alter/destroy original, otherwise ignore and return
    4. Notify listeners of update