PROBLEM
Agent orchestration answers what step runs next, but teams still need explicit policy around which actions are valid in a given context.
USE CASE
Agent tool selection
Govern when an agent may propose or invoke a tool without turning the behavior system into an agent framework.
OLD WORKFLOW
Tool descriptions and prompt instructions carry both capability discovery and policy, making authority difficult to separate.
EXAMPLE
An agent may propose a refund tool only when the registered order state and policy scope permit it; otherwise the action boundary remains blocked or escalated.
VIRA WORKFLOW
Keep evidence, authority, evaluation, and release separate.
- 01
Define a Behavior Point around tool or action selection.
- 02
Use typed signal and action registries for the allowed decision surface.
- 03
Resolve behavior before the agent action boundary.
- 04
Keep framework execution native.
- 05
Trace the resulting decision and capture corrections through Teach.
WHAT IS GOVERNED
- Behavior Point
- Action registry
- Signal provenance
- Hard guards
WHAT IS MEASURED
- Selected modules
- Action decision
- Trace correlation
- Conflict outcome
WHAT CAN FAIL
Failure states are part of the design.
- An action is not present in the governed registry.
- A required signal came from an untrusted model extraction.
- The Behavior Point has no valid binding.