Knowledge
The governed sources, context and evidence a Specialist may use for its defined work.
How it works
How a Specialist Works
Start with a defined capability, deploy your own persistent worker, then decide when it is ready to work.
From published Specialist to active Bro
Deployment, configuration and activation are separate so each decision is visible.
- 1
Choose
Review the Specialist's job, version and boundaries.
- 2
Authenticate
Sign in or register without losing the Specialist you selected.
- 3
Deploy
Create your Bro in Draft, bound to that exact Specialist Version.
- 4
Configure
Name it and review the available preferences, access and delivery choices.
- 5
Activate
Explicitly make the Bro available for work. Email remains a separate delivery choice.
- 6
Work
Give it a defined need; it performs bounded work and stores its governed history.
Governed capability
What defines a Specialist
Access
The information and connected resources it is permitted to read—never access it simply assumes.
Actions
The bounded work it may perform and the results it may create or deliver.
Approvals
The layered authority checks that decide what is allowed, what needs your approval and what remains prohibited.
Approvals are the public-facing way to understand authority. Underneath, authority is checked in layers: platform rules, Specialist rules, Bro lifecycle, configuration, user authorization, external permissions and safety controls.
Three different things
General AI chat
A flexible conversation tool. It is not the governed product object that defines a Big AI Bro Specialist or your persistent Bro.
Specialist
The platform-owned, published capability: a defined job, governed boundaries and an exact version.
Your Bro
Your persistent deployment: owned by you, configured for you and tied to a reconstructable history.
Direct answers
Common questions
What is an AI Specialist?
A Specialist is a platform-owned, governed, tested and versioned AI capability built for a defined kind of work.
What is a Bro?
A Bro is your persistent, owner-specific deployment of one exact published Specialist Version, with its own configuration, lifecycle and work history.
Does deployment start the Bro?
No. Deployment creates the Bro in Draft. You review its setup and explicitly activate it in a separate step.
Does a Bro get access to my accounts automatically?
No. Access is bounded and must be explicitly authorized. A Specialist cannot assume access simply because it would be useful.
What happens when a Specialist is updated?
Your existing Bro remains bound to the exact Specialist Version it was deployed from. A newer version never silently migrates it.
Can a Specialist take any action it wants?
No. Its permitted actions and layered approval boundaries are governed. Some actions require human approval and others remain prohibited.
Ready to see a defined Specialist?
Browse the published catalogue, then review a Specialist's purpose, activities and boundaries.