File size: 2,681 Bytes
da84c63
 
4719066
da84c63
 
 
 
4719066
da84c63
4719066
 
da84c63
 
 
4719066
 
 
da84c63
 
4719066
da84c63
4719066
da84c63
 
 
4719066
da84c63
 
4719066
da84c63
4719066
da84c63
 
 
4719066
da84c63
 
 
 
4719066
da84c63
 
 
4719066
 
da84c63
 
 
 
 
 
 
4719066
 
 
da84c63
 
 
 
 
 
 
 
4719066
 
 
da84c63
 
 
 
 
 
 
 
 
 
 
 
 
 
4719066
 
 
da84c63
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
name: orgos-openenv
version: "2.0.0"
description: >
  OrgOS is a multi-app enterprise RL environment where an agent completes
  business workflows across Jira, Zendesk, Salesforce, and Workday.
  Between episodes, schema drift renames fields and policy drift tightens SLAs,
  forcing agents to generalize rather than memorize.

author: tanvibisht
tags:
  - openenv
  - enterprise
  - multi-app
  - schema-drift
  - rl

tasks:
  - id: workflow_a
    name: "Customer Bug Fix"
    difficulty: easy
    max_steps: 15
    description: >
      Triage a customer bug report end-to-end: acknowledge the Zendesk ticket,
      create a linked Jira issue, assign it to an engineer, log the SLA event
      in Workday, and query Salesforce for account health. Support role only.

  - id: workflow_b
    name: "Employee Onboarding"
    difficulty: medium
    max_steps: 20
    description: >
      Onboard a new employee: create their Workday record, provision Jira access
      based on role, add them to the correct Salesforce territory team, and
      create their Zendesk support profile. Manager role required.

  - id: workflow_c
    name: "Churn Risk Alert"
    difficulty: medium
    max_steps: 18
    description: >
      Respond to a churn risk signal: flag the account in Salesforce, escalate
      to a Zendesk ticket, create a Jira tracking issue, and log the SLA event
      in Workday. Support role. Policy drift may tighten SLA thresholds.

api:
  routes:
    health: GET /health
    reset:  POST /reset
    step:   POST /step
    state:  GET /state
    docs:   GET /docs
    schema: GET /schema/apps

reward:
  range: [0.001, 0.999]
  partial_rewards: true
  terminal_bonus: 0.20
  components:
    workflow_completion:   0.30
    rule_compliance:       0.25
    schema_adaptation:     0.20
    efficiency:            0.15
    policy_drift_handling: 0.10

observation_space:
  fields:
    - done: bool
    - reward: float
    - current_score: "float in [0.001, 0.999]"
    - workflow_id: "A | B | C"
    - step_count: int
    - app_states: "dict[app_name, str] β€” preview of each app's records"
    - workflow_goal: str
    - completed_steps: "list[str]"
    - pending_steps: "list[str]"
    - schema_hints: "dict[str, str] β€” e.g. {\"jira.priority\": \"severity\"}"
    - active_rules: "dict β€” current SLA thresholds and RBAC rules"
    - rule_violations: "list[str] β€” violations from last action"
    - reward_breakdown: "RewardBreakdown β€” 5-component score snapshot"
    - message: "str β€” feedback from last action"

action_space:
  fields:
    - app: "jira | zendesk | salesforce | workday"
    - operation: str
    - args: "dict β€” operation-specific arguments"