-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
* 20240604 @Mookse - teams() route - teams(teamId) returns a fully formed team from server with new bots (when instructions provided) * 20240604 @Mookse - fix bot-bar `setActiveBot` - cosmetic * 20240604 @Mookse - fix duplicate team members return * 20240604 @Mookse - botBar reordered * 20240605 @Mookse - teams must be active * 20240605 @Mookse - default mods * 20240605 @Mookse - create (non-custom) bot frontend - diary updates * 20240605 @Mookse - imagining `share memory` * 20240606 @Mookse - story updates * 20240606 @Mookse - minor cosmetics * 20240606 @Mookse - fetchShadows() - ignite shadow: member-version (wip) * 20240607 @Mookse - `shadow` initial endpoint * 20240607 @Mookse - add processingBotId to payload (so that frontend can determine if it should setActive) * 20240607 @Mookse - front-end receives message about updating from agent shadow * 20240607 @Mookse - shadow cosmetics * 20240607 @Mookse - biographer openai function definitions * 20240607 @Mookse - now _that's_ an error * 20240607 @Mookse - updateSummary() **note**: wip as thread got stopped * 20240608 @Mookse - updates summary * 20240608 @Mookse - remove dataset after shadow triggered - add `proxy` endpoint to shadow ideas * 20240608 @Mookse - `globals.getGPTJavascriptFunction`: `getSummary`, `updateSummary` - `updateBotInstructions` route - on setActiveBot checks versions and updates as needed * 20240609 @Mookse - cosmetic * 20240609 @Mookse stable wip kicking off memory is correct, need tuning of instructions or alternate scene-stepwise motion, no problem small error left in frontend for more testing but time to save * 20240618 @Mookse - cosmetic: file under "the right evocation can make all the difference" * 20240618 @Mookse - cosmetic in dribs and drabs * 20240618 @Mookse - frontend 'next' fix
- Loading branch information
Showing
17 changed files
with
1,522 additions
and
371 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
/* imports */ | ||
import { | ||
activateBot, | ||
interfaceMode, // @stub - deprecate? | ||
upload, | ||
} from './functions.mjs' | ||
/* module export functions */ | ||
async function collectMemory(ctx){ | ||
// @todo - implement memory collection | ||
} | ||
async function improveMemory(ctx){ | ||
const { iid } = ctx.params | ||
const { Globals, MyLife, } = ctx | ||
const { avatar, } = ctx.state | ||
if(!Globals.isValidGuid(iid)) | ||
return ctx.throw(400, 'Invalid Item ID') | ||
ctx.body = await avatar.reliveMemory(iid) | ||
} | ||
/** | ||
* Reliving a memory is a unique MyLife `experience` that allows a user to relive a memory from any vantage they choose. The bot by default will: | ||
* @param {Koa} ctx - Koa context object. | ||
* @returns {Promise<object>} - livingMemory engagement object (i.e., includes frontend parameters for engagement as per instructions for included `portrayMemory` function in LLM-speak) | ||
*/ | ||
async function reliveMemory(ctx){ | ||
const { iid } = ctx.params | ||
const { Globals, MyLife, } = ctx | ||
const { avatar, } = ctx.state | ||
if(!Globals.isValidGuid(iid)) | ||
return ctx.throw(400, 'Invalid Item ID') | ||
ctx.body = await avatar.reliveMemory(iid) | ||
} | ||
/** | ||
* Living a shared memory is a unique MyLife `experience` that allows a user to relive a memory from any vantage the "author/narrator" chooses. In fact, much of the triggers and dials on how to present the experience of a shared memory is available and controlled by the member, and contained and executed by the biographer bot for the moment through this func6ion. Ultimately the default bot could be switched, in which case, information retrieval may need ways to contextualize pushbacks (floabt, meaning people asking questions about the memory that are not answerable by the summar itself, and 1) _may_ be answerable by another bot, such as biogbot, or 2) is positioned as a piece of data to "improve" or flesh out memories... Remember on this day in 2011, what did you have to eat on the boardwalk? Enquiring minds want to know!) | ||
* @param {Koa} ctx - Koa context object. | ||
* @returns {Promise<object>} - livingMemory object. | ||
*/ | ||
async function livingMemory(ctx){ | ||
const { iid } = ctx.params | ||
const { Globals, MyLife, } = ctx | ||
const { avatar, } = ctx.state | ||
if(!Globals.isValidGuid(iid)) | ||
return ctx.throw(400, 'Invalid Item ID') | ||
ctx.body = await avatar.livingMemory(iid) | ||
} | ||
/* exports */ | ||
export { | ||
collectMemory, | ||
improveMemory, | ||
reliveMemory, | ||
livingMemory, | ||
} |
Oops, something went wrong.