Role Assistants turn a Business Role into governed AI-assisted work — Sales Assistant, Project Assistant, Finance Assistant — that helps an identified person complete recurring work using approved enterprise context, governed capabilities, and Evidence.
This is the third pillar of AI Fabrix. Enterprise Knowledge supplies business context; Operational Trust applies boundaries; Role Assistants perform governed work; Evidence Fabrix proves the outcome.
A Role Assistant is human-owned and role-scoped. It is not a generic agent platform, free-form chatbot, or prompt-orchestration product. AI can recommend, prepare, and request work. It cannot grant itself authority.
Why it matters
Enterprises do not need another collection of agents assembled from prompts, arbitrary tools, and application credentials. They need AI that understands a defined business outcome, stays inside the active person’s authority, and produces an inspectable result.
The Business Role — not the chat persona — is the operating boundary: what work may be requested, which approvals apply, and what must be evidenced. Dimensions and Operational Trust decide which records may appear in that work. Together they shape permitted business context.
Without Enterprise Knowledge, an assistant would lack business meaning. Without Operational Trust, it would lack authority. Without Evidence Fabrix, the organization could not learn from completed work.
How assistants are created
Assistants are generated from approved enterprise definitions — not hand-built as custom chatbots:
Describe outcome + Business Role + Knowledge + Trust + Evidence
→ Generated candidate (not yet authority)
→ Validate and test for intended scope
→ Make available to the Business Role
Generation produces a versioned candidate, not operational authority. Teams validate and test before an administrator makes an approved version available. Availability does not widen the user’s existing authority. Lifecycle: Role Assistant status and availability. Creation detail: How Role Assistants are created.
Business context replaces prompt engineering
Assistants are guided by Business Role, task type, resource type, and governed capabilities — not by perfect prompts. When metadata and relationships are modeled well, assistants need less prompt tuning because context is already governed. See Business context replaces prompts.
Perform governed work
Verify person + Business Role
→ Resolve permitted business context
→ Retrieve permitted knowledge
→ Apply rules and Evidence requirements
→ Request a governed capability
→ Human approval when required
→ Preserve the actual result
The approved interface (Teams, Copilot, customer app, and similar) provides interaction. AI Fabrix retains the governed business capability. Enterprise Runtime may execute, wait, complete, or stop safely. Assistants request capabilities; they do not bypass approval or override governance.
The interface can change. The governed business capability remains with the enterprise.
Conversation-first work
People normally begin with a business objective in their preferred conversation channel. Simple Ask and Approval tasks stay in the conversation. The temporary Review Workspace opens only for rich review. Detail: Conversation-first work and Human tasks, approvals, and Why.
Skill growth and Evidence
Skill levels show maturity; promotion reflects useful outcomes — not expanded authority. Completed work can reveal improvements. Evidence may propose improvement; it cannot silently change a released Role Assistant. Material change creates a new candidate and returns through validation and approval. See Skill levels and promotion and Role Assistants, Evidence, and governed execution.
Limits
Full task flows, skill promotion, and impact dashboards vary by deployment. See Evidence Fabrix for what is live in your environment.
Example
An account manager prepares a customer renewal. The Renewal Assistant assembles permitted customer and agreement context, retrieves pricing rules, identifies gaps, prepares draft material, requests an approved operation, routes commercial exceptions to the authorised approver, and preserves completed, denied, waiting, or safely stopped results with Evidence. The account manager retains responsibility for the outcome.
Business value
Role Assistants help organisations move from generic AI interaction to repeatable business work, generate capabilities from reusable definitions instead of copying prompts and tool lists, test before release, keep human decision points explicit, and improve through governed Evidence without silently changing released behaviour.
One-line summary
Role Assistants turn a Business Role into a human-owned, governed capability — recommend, prepare, and request approved work under Operational Trust.