Skip to content

Commit 56ef02f

Browse files
authored
docs: clarify Explore harness metric fit (#1730)
1 parent 17e91ff commit 56ef02f

2 files changed

Lines changed: 10 additions & 0 deletions

File tree

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -197,6 +197,12 @@ credentials, or AB/canary gates.
197197
LoopX will plan before writing state, then create ordered P0/P1/P2 todos that
198198
make the algorithm, infra, validation, and human gates visible.
199199

200+
This Explore-style harness works best when the task has a measurable offline
201+
eval, baseline, treatment, and guardrail metrics. It is not recommended for
202+
open-ended tasks or scenarios where the evaluation metric cannot be quantified
203+
reliably, because the loop depends on comparable metrics to decide whether an
204+
exploration branch actually improved the result.
205+
200206
<details>
201207
<summary>Example visible todos</summary>
202208

README.zh-CN.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -348,6 +348,10 @@ Result Layer 把探索中的 `node`、`edge`、`finding` 记录成 public-safe
348348
Harness 读取这张图、open todo、ownership、capability 和 write-scope 信息,生成只读的
349349
todo branch plan 或 worker lane plan。
350350

351+
适用边界:Explore Harness 依赖可量化的评估指标来比较 baseline、treatment 和
352+
guardrail。对于开放任务,或者评估指标无法准确量化的场景,不推荐直接使用这个
353+
harness;这类问题更适合先沉淀成人工判断、定性研究或更小的可度量子问题。
354+
351355
```bash
352356
loopx explore node --goal-id <goal-id> --title "Map the next frontier"
353357
loopx explore finding --goal-id <goal-id> --title "Confirmed reusable contract" --node <node-id>

0 commit comments

Comments
 (0)