crestapps-core-ai-personas

CrestApps.Core AI Personas

A persona says who the assistant is: its instructions, the name it uses, its language, voice and avatar. The profile's system message and prompt templates still say what it does. A resource links to one optional persona by its technical name, so editing the persona changes every profile, interaction and template that links to it from the next message. Personas are not AI templates: a template is copied when used, a persona stays linked.

Guidelines

• Personas are opt-in. Without AddPersonas(...), persona links are kept but ignored and chats run with the profile's own instructions and voice.
• Link by Name, never by item id. Names survive export and import across tenants; ids do not. A persona's name cannot change once saved.
• Keep business rules in the profile. The persona block comes first in the system message, so the profile's rules win a conflict.
• Greetings stay with the profile's welcome message so one persona can serve profiles that open differently.
• Resolve personas only through IAIPersonaResolver (or the service-provider helpers) so chat, chat interactions, realtime and voice behave the same.

Registration

builder.Services.AddCrestAppsCore(crestApps => crestApps
    .AddAISuite(ai => ai
        .AddOpenAI()
        .AddPersonas(personas => personas
            .AddYesSqlStores()          // or .AddEntityCoreStores()
            .AddEmbeddedPersonas(typeof(Program).Assembly))
    )
);

AddPersonas (or services.AddCoreAIPersonas()) registers IAIPersonaManager, IAIPersonaResolver, the persona catalog handler, AIPersonaCompletionContextBuilderHandler and AIPersonaFileSystemProvider, which reads Templates/Personas in the content root. A YesSql host also creates the index table once with schemaBuilder.CreateAIPersonaIndexSchemaAsync(yesSqlStoreOptions) next to its other index tables.

What a Persona Holds