Purpose
Operators need a clear meaning for Draft, Active, and Suspended on Role Assistants — and how generation relates to those badges. This page is the product law for lifecycle status. It is not a skill-tier guide and not an agent builder.
Draft is the candidate state. Generation creates an inspectable candidate — not operational authority. Make available is the release gate after validation. Availability does not widen the user’s existing authority.
Why it matters
Without sticky Draft rules, regenerating Enterprise Knowledge or publishing an LLM provider can quietly move assistants back into service. Without Suspended as a system-only state, operators invent manual suspend controls that fight automation. Clear status keeps certification, generation (candidate), and day-to-day availability separate.
How it works
Lifecycle badges
| Badge | Meaning |
|---|---|
| Draft | Not offered for use. Sticky after Make unavailable until an operator makes it available. |
| Active | Published and available for users with the matching business role. |
| Suspended | Published but with no live capability surface. System-only — there is no manual Suspend action. |
Skill signals such as Trusted or Expert are not lifecycle badges.
Operator actions
| Action | Effect |
|---|---|
| Make available | Leave Draft; put the assistant into Active when capabilities exist (or Suspended if published with none). |
| Make unavailable | Force Draft. Automatic generation must not leave Draft until Make available. |
Generation
Business role + domain Enterprise Knowledge publish → Role Assistant compiled
→ Operator Make available → Active (when capabilities exist)
→ Users with the role receive the assistant
Business-domain Enterprise Knowledge publish may create or refresh Role Assistants and their business capabilities. Operators still decide when Draft enters Active.
What must not change Role Assistant status
- Publishing an LLM provider
- Regenerating unified LLM Enterprise Knowledge
- Treating LLM call / embed as Role Assistant capabilities
LLM access stays on the governed enterprise LLM surface. See Enterprise LLM governance.
Automatic rules (summary)
- Draft stays Draft until Make available (except intentional brand-new publish at create).
- Active ↔ Suspended only while the assistant is already published, based on live capabilities.
- Suspended never auto-becomes Draft.
Example
An operator moves four Sales Assistants to Draft with Make unavailable. Later someone re-publishes an LLM provider. Unified LLM Enterprise Knowledge regenerates. Those Role Assistants remain Draft. When business CRM knowledge is certified and capabilities return, the operator uses Make available — then they become Active if capabilities are present.
Business value
Status law keeps human authority over who is in service while the platform keeps capabilities current. Generation stays continuous; availability stays intentional.