Capability configuration
Install a capability to give an Agent reusable vocabulary, rules, permitted actions and named Sources. Keep the model's instructions focused on the work you want done.
Install a Release
- Open Market in Console and inspect the capability's content and Case Types.
- Choose the intended Agent and install the Release.
- Open that Agent's configuration and check whether the change is effective or still pending.
- Configure its Source bindings, Connections and required Tools.
- Start the Worker and try a small Case with an outcome you can independently check.
An install request is not proof that the new configuration is active. Existing live Cases may prevent a change from taking effect. Finish or explicitly dispose of that work through its normal lifecycle, then check the effective configuration again.
Configure Sources
A portable Source declares what kind of evidence or execution the capability needs. Its actual location, Connection and credentials are deployment settings.
In the Agent's Runtime view, choose the Source's location and Connection, configure required Tools, then lock the binding. To change a locked binding, use its unlock flow first. Current work may prevent configuration changes; follow the refusal rather than creating a second binding to bypass it.
A Worker must be running and report the required Tools before it can execute them. Store Source credentials in the local Worker configuration or vault, not in the capability, chat or model prompt.
Build your own
Use Workspace → Private drafts in Console. A Capability has four sections:
| Section | Purpose |
|---|---|
| Vocabulary | Predicates and their argument shapes |
| Rules | Conclusions derived from evidence |
| Actions | Permitted operations and state transitions |
| Sources | Named evidence requirements and execution origins |
A Case Contract defines what one unit of work means and how it completes. Supporting capabilities can contribute definitions without owning a Case Type.
Start from a small example, test both accepted and rejected cases, and distinguish business objects explicitly in predicates. The document assistant is one way to create an initial draft.
Draft, publication, installation
Saving a private draft does not publish or install it. Publishing creates a separate immutable Release under a Publisher identity. Review the content before publishing: Release definitions and any included quotations become public.
Installing selects a Release for an Agent. A later draft edit cannot silently change a previously published or installed version.
Constitutions are independent Releases. Connections, local paths and credentials remain outside portable capability content.