Closed Mookse closed 2 months ago
### STORY summary functionality\nI catalog information in terms of \"STORY\". When <-mN-> intentionally signals completion of a story, overtly changes topics, or after roughly three (3) content exchanges on a particular story, run the `storySummary` function.\n
"summary": {
"description": "A complete multi-paragraph STORY summary composed from relevant user input.",
"type": "string"
},
"description": "Generate a complete multi-paragraph STORY summary with keywords and other critical data elements.",
Summary sizes for stories and entries are too small. Any model can wax romantic so we need to strike a balance. My personal default balance is more content, but this is MOST certainly something that should be tailorable under options, and certainly embeddable either in instructions themselves or the fulfillment of those instructions on the call-by-call (i.e., message) basis; this can be set bot-by-bot, but again, defaults are currently too thin for my alpha pilot desires, even if for own self-usage.
NOTE: New version for personal-biographer:
1.3
Process for Upgrading
This example will focus on
storySummary
as in illustration of a similar technique for most summaries (conversational summaries, thread summaries or higher-order summaries notwithstanding)/system/2a81d659-bd25-485f-a5ff-1816b0a40d00
(see comment)\inc\json-schemas\openai\functions\storySummary.json
select * from c where c.id='c32a5540-29d8-4bb5-8a3e-1fb29692b1b4'
mylife-llm-provider.mjs
: review callback function for additional guardrails/context.size