Role Assistants improve from validated Evidence generated by completed governed work — not from prompts or conversation history. Each reusable outcome strengthens patterns the organization can trust.
Evidence may propose improvement; it cannot silently change a released Role Assistant. A material change creates a new candidate and returns through validation, certification, and Make available.
Why it matters
Enterprises need AI that gets better at recurring role-based work without expanding authority. Learning must be tied to verified outcomes — including accepted, corrected, rejected, escalated, waiting, denied, and safely stopped — after validation and certification when the knowledge is meant to be reused.
How it works
Task → Business result → Validate → Certify when reusable → Pattern → Propose improvement → Better future work
This is a business-testing lifecycle, not a model-testing loop: a business specification becomes a generated capability, business validation cases prove that capability against the specification, release makes it available, execution produces outcomes, and validated Evidence closes the loop into an improved definition.
Business specification → Generated capability → Business validation cases → Release → Execution → Evidence → Improved definition
The underlying model can change — a new version, a different vendor, a retrained skill — without breaking this loop. What stays reusable is the business expectation and the governed definition it is tested against, not any single model's behaviour. See Business meaning as governed content for why that definition is governed content, not application code.
Evidence aggregates by Business Role, task type, capability, and resource type. Successful patterns increase confidence; repeated corrections highlight data or process gaps. Skill levels make improvement visible to users and managers.
Learning improves quality and reliability. It does not grant new permissions or remove approvals.
Limits
Evidence aggregation, skill snapshots, and promotion workflows vary by platform version. Confirm Role Assistant evidence features are certified live in your environment before treating promotion as operational policy.
Optional post-completion learning (a separate governed Task after work completes) is not on by default. There is no guaranteed Suggested Evidence queue in every deployment. Evidence may propose improvement; it cannot silently change a released Role Assistant.
Example
After many accepted pipeline reviews, a Sales Assistant recognizes common missing-owner patterns faster — because Evidence from prior tasks proved those patterns useful, not because it memorized chat phrases. A proposal to change instructions still goes through governance before release.
Business value
Continuous improvement grounded in governed outcomes — aligning AI maturity with business trust while keeping operational change under human control.