What it proves
Buyers can see what this pillar changes in the client app, which work it supports, and how evidence stays attached to the outcome.
Cores
Reusable assistants with model lanes, prompts, execution paths, retrieval posture, and tool scope.
Approved sources Files, apps, sites Core policy Scope and model lane Grounded answer Cited response path Visible activity Trace and usage proof
How teams inspect it
Each workflow points to visible product surfaces: active scope, source health, answer activity, cited passages, configuration controls, and usage impact.
Where it connects
This pillar links into feature pages, demos, proof sections, and pricing comparisons so teams can move from platform claim to concrete behavior.
Cores features.
These pages give buyers a path from platform claim to concrete client-side behavior.
Custom AI Cores
Saved assistants package prompts, models, datasets, tools, defaults, and access rules.
Open feature page Planner workflowComplex requests can run through structured evidence-gathering steps before answering.
Open feature page System prompt editorUsers configure Core instructions directly.
Open feature page Core execution pathCores can use direct chat or planner-based execution.
Open feature page Core dataset scopeA Core can use no datasets, all datasets, or selected datasets.
Open feature page Retrieval strategy selectionChoose graph, vector, keyword, fuzzy, or plan-default retrieval.
Open feature page