Glossary

Basic Studio Concepts

This section introduces core terms that help users understand how Promethist Studio functions as a platform for building conversational AI applications.

  • Promethist Studio – A SaaS designed to create, manage, and deploy intelligent digital assistants (Personas). It enables users to build AI-powered applications using modular, reusable components called assets.

  • Asset – The fundamental unit of content and functionality in Promethist Studio. Assets include Activities, Skill Sets, Personas, Characters, Identities, and more. They are used to build the structure and behavior of conversational applications.

  • Persona Composition – The model by which a Persona is constructed in the Studio. Each Persona is formed by combining three types of assets: a Character (behavior), a Role (function), and an Identity (appearance; life-story, principles, beliefs).

  • Modularity – A principle of Promethist Studio’s architecture where each asset is self-contained and reusable. Assets can be mixed, matched, and updated independently to support agile development and iteration.

  • Publishing – The process of making your saved changes available to others by adding them to the shared destination changeset. This allows your updates to be visible and usable in applications.

  • Environment – An isolated deployment context within a project (e.g., development, staging, production). Each environment can have different configurations and engine access settings.

  • Engine – The underlying runtime system that interprets and executes application logic, enabling Personas to interact with users. The engine uses defined assets and prompts to drive conversation.

  • Testing Tools – Built-in Studio interfaces that allow users to simulate conversations, preview avatars, and test applications in various modes (e.g., chat, QR, or avatar view).

  • Project – A workspace that contains a complete set of assets and settings related to a specific application or product initiative. Projects support version control and team collaboration.

  • Tenant – An organizational structure in Promethist Studio that groups multiple projects under a single business or team. It defines the administrative boundary and access control.

  • Prompt – A message, instruction, or expression provided to the Persona to guide how it responds to the user. Prompts are defined within Activities and Skill Sets, and are typically categorized as start, main, or end prompts.

  • Session – A bounded interaction between a user and a Persona, framed by the start and end of a conversation. During a session, all prompts, decisions, and conversation state are tracked to maintain continuity and context.

Core Assets

This section defines the fundamental building blocks used to create AI-powered applications in Promethist Studio.

  • Applications – A complete conversational product composed of one or more Personas.

  • Personas – The digital assistant created by combining a Character, Role, and Identity.

  • Roles – Encapsulates the Persona’s business logic and functional responsibilities.

  • Characters – Defines the tone, style, and behavioral traits of a Persona.

  • Identities – Represents visual and contextual presentation, including avatar, voice, and appearance.

  • Skill Sets – A group of Activities organized for a specific purpose, categorized as either social or business.

Social skill sets involve interpersonal and emotional abilities, helping personas build connections and communicate effectively.

Business skill sets are tied to specific roles and define the professional capabilities required to perform tasks or fulfill job responsibilities within the application.

  • Activities – A self-contained conversational or functional unit executed by the Persona.

  • Knowledges – External information or data sources linked to specific Persona use cases.

  • Archetypes – A predefined behavioral model that guides the Persona’s expression and tone.

Activity and Skill Set Configuration

This section outlines the parameters that control how Activities function and how they are orchestrated within Skill Sets. These configurations influence the timing, behavior, and flow of conversational logic in Promethist Studio.

Activity Parameters

These settings are defined when creating an individual Activity and govern what the Persona says and how it behaves during execution.

  • Main Prompt – The directive the Persona follows when the activity is triggered. It defines the specific message or action the Persona performs in response to this task.

  • End Prompt – A condition that represents successful completion of the activity. Once met, the Persona deprioritizes this activity for the rest of the session to avoid repetition.

  • Should End Conversation – A flag that, when enabled, ends the current conversation session after the activity completes. Typically used for farewells or transactional endpoints.

Skill Set Configuration

These settings are configured within a Skill Set and control how and when an activity is selected for execution, based on conversation context or system logic.

  • Interaction Node – A structural element in a Skill Set that is used to link interaction units such as Activities and Dialogues.

  • Activity Node – A specific type of Interaction Node that connects directly to a single Activity and defines its triggering logic.

  • Start Prompt – A natural language condition that defines when an Activity becomes contextually relevant. Used to match user intent or conversational cues.

  • Start Code – A programmatic condition (typically Kotlin) that is evaluated at runtime. If the code returns true, the activity is considered for execution; if false, it is skipped.

  • Is Interim – A setting that determines whether the system should automatically continue to the next Activity without waiting for user input. Useful for chaining system-driven steps.

Developer Tools

  • Populate Entities – Interface controls for bulk creation of Activities, Skill Sets, Roles, and related assets.

  • Add Tenant / Add Project – Administrative tools for multi-tenancy and isolated workspace setup.

  • Migrations – Tools for transferring asset structures (such as Skill Sets) between environments or versions.

  • Events – System events and triggers used in custom logic and workflows.

  • Kotlin Lang Server – Integration for executing and validating Kotlin-based server logic.

Project Versioning and Deployment

  • Main Branch / Remote / Repository – Version control fields for linking to external Git repositories.

  • Environment – A runtime deployment configuration (e.g., development, staging, production).

  • Engine URL / Engine API Key – Connection details for running applications through Promethist Engine.

  • Create Environment – Function to define and configure a new environment context.

Collaboration, Testing, and Operational Analysis

This section addresses team workflows, real-time testing, and data-driven performance review.

User and Access Management

  • Project Members – Users who are granted access to a specific project space.

  • Status – Indicates the participation state of a member (e.g., Accepted, Active).

  • Change Role / Remove from Project – Actions to manage member permissions and participation.

Testing and Simulation

  • Publish – Activates changes made to project assets.

  • Testing Options:

    1. Chat Tab – Allows testing the Persona’s conversational behavior through text-based interactions.

    2. Avatar Tab – Allows testing the Persona’s visual representation and animations.

    3. QR Tab – Enables testing through mobile or web clients via QR code access.

Monitoring and Logs

  • Usage – Reports on interaction volume, frequency, and user engagement.

  • Transcripts – Logged conversations between users and Personas for quality review.

  • Performance – Data metrics including latency, success rates, and efficiency.

  • LLM Logs – Logs of language model activity to support debugging or refinement.

Configuration and Settings

  • Tags – Custom labels used for filtering, sorting, or logic conditions.

  • Voices – Set of available synthetic voices for Personas.

  • Libraries – Custom or reusable code and logic modules (feature-dependent).

  • Settings – General application or environment-level configuration options.