Create Obscure Functionality

[Mookse]

Diary Bot Function: Obscure

Create the functionality to meet the functional specifications for obscure to obscure relationships or entries initially by substituting proper names with their first letter.

Member Version

• routes.mjs create members obscure
• functions create obscure
• mylife-avatar.mjs: obscure()
• mylife-agent-factory.mjs
  • get item
  • send summary to LLM, ask for coding in response? [i.e., who is who?]; ergo factory has correct mbr_id and has access to generic LLM in modular code
  • validate response
  • process response
  • save response
  • return instructions and saved item

API Version

• routes.mjs create api obscure
• api-functions.mjs create obscure: validate, extract, and pass to MyLife
• core.mjs class MyLife
  • create proxy Member Avatar (bot-factory for now?) to address obscuration; note: interestingly it looks like the proxy Bots (which occur understandably in factory, i.e., not to be accessed without trace) all require and are infused with the modular Generic Version as I can't tell if it's overwritten, but might be able to remove property this.#llmServices in all factory instances (and just rely on modular version when it is appropriate)
  • call obscure on bot-factory
• Diary Bot yaml for API

Bot Version

• diary bot instructions should include the option to obscure which requires the itemId (see comment)
• define obscure function in globals.mjs (see comments)
• mylife-llm-providers.mjs add function as a callback
• note: of course bots could engineer this on their own with the CRUD ability - question is just that: afford vanilla with options to override
• side quest: general System Bot

[Mookse]

update diary-intelligence-1.0.json

### OBSCURE ENTRY\nWhen request is prefaced with `update-request` it will be followed by an `itemId`.\nIf member's request indicates they want an entry be obscured, RUN `obscure` function and follow the action in the output.\n

[Mookse]

	obscure: {
		description: "Obscures a summary so that no human names are present.",
		name: "obscure",
		parameters: {
			type: "object",
			properties: {
				itemId: {
					description: "Id of summary to obscure",
					format: "uuid",
					type: "string"
				}
			},
			required: [
				"itemId"
			]
		}
	},