Skip to main content

AI Governance

Fine-grained controls for different aspects of AI governance

Updated over 2 weeks ago

Every thunk provides settings and options to control five different "CHARM" aspects of AI governance.

Compliance and Safety

Many of the settings in this category are inherited from the particular deployment options or platform SKU of the Thunk.AI service.

Enabling the options for compliance and security checks is highly recommended, although it does add latency and cost to the execution of AI logic.

Human-In-The-Loop Collaboration

These options control how human agents interact with workflow automation. The workflow can be completely automated, or different stages of the workflow can require human intervention. These thunk-level settings can also be overriden at the level of individual workflow steps.

Automation

Most of the options in this section control the scale of resources applied to the automation work. This is important because many automated steps involve downstream resources (eg: a Google Drive file system) and aggressive concurrent workflow automation can overwhelm these downstream resources and cause rate limiting errors or failures

Reliability

The options in this section control various runtime mechanisms used to enable AI reliability.

Modularity

The options in this section control various extensibility and modularity behaviors of the system. Many of the settings in this category are inherited from the particular deployment options or platform SKU of the Thunk.AI service.

Tool and Library Configuration

The thunk designer can enable or disable entire libraries or specific tools within the libraries. Only these libraries and tools are made available to the AI agents as they execute specific AI Instructions within the thunk. Further, the designer can define constraints on how the tool should be used. For example, the web search tool can be constrained as follows: “only search within site: acme.com”.

This configuration can be setup at both the thunk level and at the level of individual AI instructions.

The choice of enabled libraries (and enabled tools within those libraries) and constraints on those tools are an important aspect of control for the thunk designer. They limit the degrees of freedom afforded to the AI agents and control the autonomy and agency of the AI agents are they execute workflows.

Did this answer your question?