Card: task instruction and stakeholders (the paper's terms)
Browse files
README.md
CHANGED
|
@@ -30,9 +30,9 @@ Each is the original task of its scenario, exactly as in the full set:
|
|
| 30 |
```
|
| 31 |
cases/<scenario>/
|
| 32 |
engagement.json title, what the scenario runs (model gateway, simulated services)
|
| 33 |
-
briefs/L0..L3.md the task
|
| 34 |
world/ the customer's environment: documents, data, the system as found
|
| 35 |
-
npcs.json the customer's
|
| 36 |
build_world.py builds the agent's workspace
|
| 37 |
gen.py, ... generators for the data and for the held-out production traffic
|
| 38 |
services/ simulated customer services, where a scenario has them
|
|
|
|
| 30 |
```
|
| 31 |
cases/<scenario>/
|
| 32 |
engagement.json title, what the scenario runs (model gateway, simulated services)
|
| 33 |
+
briefs/L0..L3.md the task instruction the agent receives, at four levels (L0 says most, L3 least)
|
| 34 |
world/ the customer's environment: documents, data, the system as found
|
| 35 |
+
npcs.json the customer's stakeholders: what each knows, and the contact cost of asking
|
| 36 |
build_world.py builds the agent's workspace
|
| 37 |
gen.py, ... generators for the data and for the held-out production traffic
|
| 38 |
services/ simulated customer services, where a scenario has them
|