Skip to main content
An Automation’s Policy is its list of setup questions and their typed answers: an approval threshold, a mailbox, a list of senders who always get a reply, a routing table. A person can change an answer without editing any AOP, and the next Run uses the new value. Put the values your team expects to tune in Policy, and keep the AOP for the steps. Policy belongs to an Automation, so these commands work on teams that have moved to Automations.

​
See the Policy

Add --json to get each field’s ID, key, type, and current value.

​
Add a question

The field’s key is its label in lowercase with underscores (VIP senders becomes vip_senders), with a number appended if that key is taken. The output prints the new field’s ID and key. --binding records how the answer is meant to be used. It doesn’t limit which Runs receive it.

​
Answer a question

--value is read as JSON when it is valid JSON, and sent as plain text otherwise. --clear removes the answer and does not put a default back, so a Run that reads the question is refused until it is answered again. To go back to a default, set it with --value; config-fields --json shows it as default_value when the question has one. Each type expects this shape:

​
How an Agent reads Policy

Reference a question in the Agent’s AOP with a tag that carries its key and label:
Saving the AOP links the question to that Agent’s Revision. When a Run starts, it receives the current answer to every linked question in a block appended to its instructions, so the AOP never needs to hold the value itself.
A Run is refused while a question it reads has no answer: “This step reads 1 Policy question that nobody has answered: vip_senders. Answer them, or stop reading them in Setup.” Answer the question before testing.
Agents read Policy but can’t change it. Answers change on the Automation’s Policy screen, with set-config-field, or through Ask Duvo when you tell it to. If an Agent needs to keep rules it learns while it runs, store them in a file or in the Agent’s memory instead.

​
Edit, hide, and organize questions

--option and --column on edit-config-field replace the whole list. --column and --type only work while the field has no answer.
Changing an Automation’s Policy needs the Builder role or above on an Automation you created, and Lead Builder or above on anyone else’s.