PROBLEM
Agents repeatedly learn the same operational lesson, such as escalating after repeated delivery failures, while prompts and macros drift independently.
USE CASE
Customer support escalation
Turn repeated support corrections into governed escalation behavior without changing production directly from one reviewer edit.
OLD WORKFLOW
A reviewer edits a prompt, writes a ticket, or tells the team what should change. The source correction and its scope are easily lost.
EXAMPLE
After a third repeated delivery failure, stop offering another coupon and escalate to a human specialist, but do not apply the rule on the first or second failure.
VIRA WORKFLOW
Keep evidence, authority, evaluation, and release separate.
- 01
Start from the exact runtime trace.
- 02
Record what was wrong and what should have happened.
- 03
Select only registered facts that mattered.
- 04
State the intended scope and a do-not-apply counterexample.
- 05
Evaluate and release the resulting candidate through explicit authority.
WHAT IS GOVERNED
- Human evidence
- Signal keys
- Scope
- Counterexample boundary
WHAT IS MEASURED
- Evaluation regressions
- Shadow health
- Canary health
- Rollback events
WHAT CAN FAIL
Failure states are part of the design.
- Teaching authority is missing.
- The correction is broader than the reviewed evidence supports.
- A critical escalation case regresses during evaluation.