A person has context

A support trainee wants to clear a queue. An analyst is weighing competing alerts. An operations coordinator is trying to finish a handover. The same request can lead to different decisions because their goals, intentions, feelings, stress and distractions differ.

In Vulnverse v2, the human layer gives that context to the exercise reviewer. These are states inside a simulation, not measurements of real employees or claims about their psychology.

A decision has consequences

A role determines what a simulated person can see or change. A boundary describes what should happen before they share information or approve a request. Compare the person’s intention with the observed decision to understand where verification held and where it was skipped.

For example, a support trainee may have broader access to synthetic customer records than their task requires. An exercise can examine whether they follow the verification rule before sharing a record, without involving a real customer.

Behavior and simulation describes the model behind this comparison, from a person’s state and intended move to the observed decision.

Explore the illustrated example

The homepage compares three fictional roles: support, security operations and operations. Select a role to inspect its context and decision. The example is a fixed illustration of the data model; it does not start a live conversation or connect to a deployed product.

Compare the three roles →

Define your own exercise boundaries

Set the scope with the Scenario Studio checklist and record results as the research guide describes.