Design and Build Core Service Models

[Mookse]

Core Service Model

The core service model(s) should reflect basic ai-narration agent abilities. Before functionality can be built, the relational architecture for where to build the logic and how to separate it out comes into play. My preference is UML, but I don't have any programs that are both free and easy to use to my knowledge.

• [x] #89
• [ ] AI-Assistant functionality development
  • [ ] #88
  • [x] #91
  • [x] #90
• [ ] AI-Story-Agent development
  • [ ] logical determination: owner? [this could ultimately get thorny, as it is the decision between visiting another member agent or crafting one's own, but keep simple for now]
  • [ ] define minimal requirements for interface and functionality
  • [ ] unique endpoints will establish UI/requirements
  • [ ] image build for story representation as part of dynamism

Out-of-Scope

add-ing an agent beyond those initially provided will not be part of this issue; this only provides for selection; presume however, that it would be implemented sensibly similarly

[Mookse]

I am originally thinking that there should be some front-end acknowledgement that you have changed the AI-Agent from Maht to AI-Narration Agent, as also independent from the personality portraying Digital Self that emulates each member in the precise effort to tell a story or answer a question... In any case, how is it best to conceive of this from an endoint standpoint? Something akin to... .../{member-account}/{ai-agent-id or name?} Therefore, relying on the session login is key, so I will either build out or leverage that architecture - remember, all members exist before validation, so any account that doesn't exist should be created...? And then later activated (as in: permissions to current build(s))

• outside of session: Maht
• inside of session, define core required agents
  • MyLife Services Agent(s)
  • Core Services
    • file ingestion
    • settings/preferences
    • Dataservices
  • AI-Narration
  • MyLife Avatar: personal core avatar
  • onDemand, create any agents available to user

[Mookse]

closed with Member-services alpha