Allocate
5 Simulation / 8
Audit

Simulation

Run batch simulations across all decision types for the selected scenario. See how parameters affect allocations and why results may differ from expectations.

Tip: Triggering Adaptive Learning

To see Surprise Escalation:

  • Use "Real API" mode with high novelty/uncertainty
  • Look for SURPRISE badge in results
  • Check governance tier escalation (Tier 3→2→1)

To trigger Override Learning:

  • Override decisions in the Audit page
  • System learns from AI→Human corrections (1.2x weight)
  • Check Settings for learning stats
Scenario: Software Development | Code changes, bug fixes, features, security patches
Change
Simulation Settings

Ready to Simulate

Configure settings above and click Run Simulation to see how decisions are allocated across all types in the Software Development scenario.

Why "Expected" vs "Got" may differ: Each decision type has typical parameter ranges that usually result in a specific allocation mode. However, the actual allocation depends on the exact parameter values and system thresholds.
  • A "Code formatting" task (typically AI) might get HYBRID if data quality is unusually low
  • A "Security vulnerability" (typically Human) might get HYBRID if confidence is high and stakes are moderate
  • Parameter variance introduces randomness that can push values across threshold boundaries