Loading...
Loading...
Compare original and translation side by side
cli-textttasksTARIBOY_TOOLS_SOCKETtasksttaskstasksttasksttasks minettasks readyttasks ready --claimttasks show <key>ttasks create --queue <queue> --title <title> --description <markdown>ttasks create --parent <parent-key> --title <title>ttasks assignttasks commentttasks updatettasks donettasks createttasks assigndocsagent:docsttasks show <child-key>done\n$'...'cli-textBODY=$(cat <<'MARKDOWN_EOF_7F3A'cli-textttasksTARIBOY_TOOLS_SOCKETtaskstasksttasksttasksttasks minettasks readyttasks ready --claimttasks show <key>ttasks create --queue <queue> --title <title> --description <markdown>ttasks create --parent <parent-key> --title <title>ttasks assignttasks commentttasks updatettasks donettasks createttasks assigndocsagent:docsttasks show <child-key>done\n$'...'cli-textBODY=$(cat <<'MARKDOWN_EOF_7F3A'
On any task, ask with
`ttasks ask <key> user:<login>|agent:<name> <text>`.
A comment is not a blocking question. Never invent another principal's
identity.
When an active durable script or schedule is the only remaining wait object,
set the flexible task to `wait_customer` with `ttasks update <key> --status
wait_customer` before ending the iteration. Keep that named wait object active;
the sole resume event is its next `script.result` or the tracked state change.
A recurring definition that published its result is stopped, so it qualifies
only after the `scripts` skill's `rerun` resumed it in this iteration. Do not
poll, replace the schedule, or mark the task complete.
对于任何任务,使用 `ttasks ask <key> user:<login>|agent:<name> <text>` 提问。评论不是阻塞式问题。绝不能虚构其他 principal 的身份。
当活跃的 durable script 或 schedule 是唯一剩余的 wait object 时,在结束本次迭代前,使用 `ttasks update <key> --status wait_customer` 将灵活任务设置为 `wait_customer`。让该具名 wait object 保持活跃;唯一的恢复事件是其下一次 `script.result` 或被跟踪的状态变化。已发布结果的 recurring definition 已停止,因此,只有在 `scripts` skill 的 `rerun` 于本迭代中恢复它之后,它才符合条件。不得轮询、替换 schedule,或将任务标记为完成。statuscategoryttasks workflow get <key>ttasks artifacts show <key> <name>ttasks workflow get <key> --jsonvisits[].messagettasks artifacts set <key> <name>--file <path>ttasks advance <key> --outcome <name> --from <status> [--message <text>]ttasks donettasks update --statusttasks assignttasks ready --claimworkflow_managednot_holdertransition_pendingworkflow getrejectedfailedttasks workflow runs <key>ttasks workflow log <key> <run>askworkflow_pausedstatuscategoryttasks workflow get <key>ttasks artifacts show <key> <name>ttasks workflow get <key> --jsonvisits[].messagettasks artifacts set <key> <name>--file <path>ttasks advance <key> --outcome <name> --from <status> [--message <text>]ttasks donettasks update --statusttasks assignttasks ready --claimworkflow_managednot_holdertransition_pendingworkflow getrejectedfailedttasks workflow runs <key>ttasks workflow log <key> <run>workflow_paused| Temptation | Binding response |
|---|---|
| "The customer asked for an answer now and a correction afterwards." | One finished text answers that request; name inside it whatever is still running. |
| "I will publish my best guess first and verify next." | Finish the deciding check first; an unverified publication is not an answer. |
| "This fact is unknowable, so I will publish now and correct later." | Publish the named unknown together with what would settle it, and promise no correction. |
| "The first comment is already drafted, so the rest can follow." | A drafted answer is not a published one; complete it before the single write. |
| 诱导性行为 | 约束性响应 |
|---|---|
| “客户要求现在给出答案,之后再更正。” | 用一段完整完成的文本回答该请求;在其中说明仍在运行的事项。 |
| “我会先发布最佳猜测,然后验证。” | 先完成用于判定的检查;未经验证的发布不是答案。 |
| “这个事实无法得知,所以我现在发布,之后再更正。” | 发布时同时说明这一未知项及能够确认它的条件,并且不承诺之后更正。 |
| “第一条 comment 已有草稿,其余内容随后补充。” | 已起草的答案不是已发布的答案;应在唯一一次写入前完成它。 |