agents-relay 1.0.80 → 1.0.81
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -22,6 +22,34 @@ For a newly created PR (`job create --head`), standalone objective Markdown is r
|
|
|
22
22
|
Any task producer — orchestrator, planner, or nested task-producing agent — must follow this contract.
|
|
23
23
|
Task producers choose semantic task properties such as objective, dependencies, worker requirements, priority, and `storySize`. They do not normally choose an adapter, provider/model, or raw timeout milliseconds.
|
|
24
24
|
|
|
25
|
+
### Task input vs result
|
|
26
|
+
|
|
27
|
+
A Task input records **what is known and what has already been decided before execution**. A Task result records **what execution discovered and what was actually done**.
|
|
28
|
+
|
|
29
|
+
Task input should include, as applicable:
|
|
30
|
+
|
|
31
|
+
- goal and observed behavior;
|
|
32
|
+
- evidence and reproduction details;
|
|
33
|
+
- constraints and acceptance criteria;
|
|
34
|
+
- **known root cause** only when it is already confirmed by the user, a prior Task, or durable evidence;
|
|
35
|
+
- **hypothesis** when a suspected cause is not yet confirmed;
|
|
36
|
+
- **proposed solution** when there is a candidate approach that the executor may validate or change;
|
|
37
|
+
- **required solution** when the user or orchestrator has already decided the implementation approach. Executors must follow it unless they discover that it is infeasible, unsafe, or conflicts with higher-priority constraints, in which case they must report the deviation explicitly.
|
|
38
|
+
|
|
39
|
+
Do not require a producer to invent a root cause or solution that is not known yet.
|
|
40
|
+
|
|
41
|
+
Task results should include, as applicable:
|
|
42
|
+
|
|
43
|
+
- **root cause** for bug, incident, failure, diagnostic, or recovery work; if an investigation cannot determine it, state that explicitly with the remaining uncertainty;
|
|
44
|
+
- **implemented solution**, describing what was actually changed or done;
|
|
45
|
+
- **deviations** from any proposed or required solution, with the reason;
|
|
46
|
+
- **validation** showing how the result was verified;
|
|
47
|
+
- relevant changed files, commits, PR comments, artifacts, or remaining issues.
|
|
48
|
+
|
|
49
|
+
For feature/refactor work with no failure to diagnose, root cause is not required. For research tasks, use findings/evidence instead of forcing root-cause language.
|
|
50
|
+
|
|
51
|
+
Keep these concepts distinct: observation is not root cause; hypothesis is not root cause; requested approach is not implemented solution; implementation is not validation.
|
|
52
|
+
|
|
25
53
|
## Worker routing order
|
|
26
54
|
|
|
27
55
|
Every new model-backed executable task follows this order:
|