tiers
Tiers: which models the app's agents think with, chosen by what the work needs rather than model by model.
On this page 6
import { tiers } from "@copilotz/team";What it keeps
It keeps 1 collection, on the record: every change to it is an event.
| Collection | Kept as | Fields |
|---|---|---|
modelChoice | documents | space, tier, custom, at |
Its named queries read for callers, as the rules let them:
| Query | Who outside runs it |
|---|---|
modelChoice.agent | people, agents for a person, keys and routines |
modelChoice.offered | people, agents for a person, keys and routines |
What it lets callers do
Of its 3 Actions, people may call 2; agents, contacts and someone signed out may call none.
| Action | Person | Agent | Contact | Anyone | Key | Routine | What it does |
|---|---|---|---|---|---|---|---|
tiers.choose | yes | no | no | no | no | no | Chooses the tier of models the app's agents use, in the org or a space. |
tiers.pick | yes | no | no | no | no | no | Picks the model one of the app's agents uses, in the org or a space. |
An agent works for a person, and calls what both may. A key calls only what its scope names. A routine is work done for a person, which they set going.
Only the app's own code calls tiers.model: its plugins, its schedules and the system.
Where it shows
It has no Views of its own: its front ends show it, tiers-web.
- What it adds to resources:
agentModel(tiers).
What it needs
Nothing to set. It reads agents, model, planTier, provider, tiers and usage, resource kinds the app and other plugins fill.
What it requires
The runtime doesn't start without chat and spaces: add them too.
It ships in a package of its own, @copilotz/team@1.0.0-rc.34, for copilotz 1.0.0-rc.34: install it beside copilotz.
Listing
It keeps every listing rule.