veronicaandfred
a480ee83dc
Co-authored-by: veronica <[email protected]>
1.5 KiB
kind, status
| kind | status |
|---|---|
| guide | active |
Configure an Interaction Instance
An interaction instance is a configurable local roster member with canonical class: interaction and matching tool_policy: interaction. “Tess” may be used as a display alias, but neither that alias nor the stable name is required or authority-bearing.
Use the validated generic roster as the safe shape. Choose a unique stable name, any descriptive alias, a supported declared runtime, explicit provider/model/reasoning, and a safe work directory. Start with:
name: interaction-example
alias: Interaction Example
class: interaction
tool_policy: interaction
lifecycle:
enabled: true
desired_state: stopped
Plan the complete agent payload with the current roster generation, then create it without --persisted-start. Creation defaults to enabled/stopped and performs no runtime action. Review the resulting roster and projection plan before any later lifecycle decision.
The interaction class is request/status only. It cannot orchestrate, issue leases, mutate the roster/configuration, grant credentials, certify validation, approve landing, or merge. Connector and channel configuration are outside roster v2; do not add connector, channel, secret, command, remote-host, or gateway fields.
See safe CRUD, identity separation, and role authority.