Human-in-the-Loop (HITL)
Our agents currently do not operate with complete autonomy, which mandates the integration of Human-in-the-Loop (HITL) processes during their creation. The HITL feature in Kyndryl Bridge is crucial for enhancing control and mitigating risks by requiring human approval for all critical AI actions.
This allows for the involvement of multiple participants in a single workflow. If a user fails to respond to a HITL request within the established timeframe, the system automatically denies it, ensuring a predictable timeout behavior that is thoroughly logged for transparency.
Agents will pause for user review in the Bridge AI Assist UI, where decisions can be either approved or denied. If there is no response within the specified timeframe, the decision is automatically denied. This procedure will continue until the full (POA) is established.
Agents involved in HITL steps will automatically defer requests if there is no action taken within a 30-minute window. Additionally, all processes must be completed within a two-hour timeframe. This aims to prevent system overload and ensures that workflows remain streamlined, even when multiple approval layers are involved.
CD process for EA review readiness
Agentic AI offers templates for developers to build their agents using the enhanced Bridge SDK, which includes features like knowledge bases and connectors. While deploying an agent is straightforward, it's crucial to ensure that only valuable agents are launched.
To avoid clutter from unused agents, we established checks in our continuous deployment (CD) process. Developers must submit a Pull Request (PR) with 5 key components.
Deployment requires 2 layers of approval prior to advancement:
- 1st - Business approval: It is currently carried out manually. A panel of 2 business executives reviews each request, accompanied by a succinct high-level description (no more than five sentences) that conveys the asset's intent.
- 2nd - Technical approval: Aimed at evaluating whether the code adheres to best practices, maintains security, and is free from issues such as hardcoding. The technical team, under the leadership of architects, is responsible for endorsing the code.
Technical / Business analysis
- What is the value to Kyndryl Teams? Describe how this agent helps address the business problem.
- What is the value to the client? Explain how to execute this automation/solution and the benefit of running this solution.
- What kind of resource utilization will this solution have? Resource utilization on the Endpoint server.
- Does this solution make any changes to the target server? Does the solution make changes to the system? Does it reboot? Is there any manual approval in play (Human-In-The-Loop) before making such a change?
- Is the agent deterministic or strictly rule‑based in its execution? Describe the controls that are in place to prevent hallucination or unintended actions. Explain whether the solution ensures predictable, auditable, and safe behavior.
Once both approvals are in place, the CD process can begin. This means the code can move from development to production, ensuring that each deployed agent is necessary and beneficial for the business.
HITL notification framework
This framework informs authorized reviewers when an agent of execution requires human input. The Reviewers can access the corresponding execution, inspect the available context and take the configured action, such as approve or reject.
When an access group is selected, the notification service resolves the users in that group and sends the notification through the configured channels. Recipient scope should be reviewed carefully to avoid sending approval requests to unnecessarily broad groups.
Workflow
To understand how the framework works, see the following steps:
- An agent reaches a configured HITL step.
- The workflow enters an action-required or pending state.
- The notification service sends an in-app or email notification to the configured recipients.
- The reviewer opens the notification and navigates the related execution.
- The reviewer checks the execution details and available input information.
- The reviewer selects an available action, such as Approve or Reject.
- The workflow records the response and continues according to its configured logic.
Solution capabilities
The solution team can configure:
- Notification channel based on what the common notification service supports.
- Individual recipients or recipient access groups.
- Email subject and message content.
- Dynamic execution information is included in the message.
- Additional labels, fields or supported HTML formatting.
- Navigation details linking the recipient to the relevant execution.
- HITL actions are available to the reviewer.
Email notification
The email notification may include:
- Account or tenant context.
- Agent or deployment name.
- Execution or workflow identifier.
- The HITL step requires attention.
- Relevant execution details.
- Available approval actions.
- Link to the associated execution.
- Additional fields configured through the notification template.
User considerations
Make sure to:
- Ensure recipients have access to the relevant Kyndryl Bridge account and execution.
- Keep notification content concise while providing enough context for an informed decision.
- Avoid using large access groups unless every member is expected to act on the request.
- Confirm that email navigation takes the user directly to the relevant execution or approval experience.