Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

ADF dispatch: unattended long runs require a machine-checkable acceptance criterion and a known-answer control run

未关闭
#968 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust

调研方向

Start by locating the task and agent definitions, the spawner, and loop detection referenced in the proposal and issue #3080. Trace how unattended dispatch is selected, then verify that missing fields and a failing control run are rejected before the real task, while acceptance progress can inform long-run detection.

由索引模型根据 Issue 内容生成。

描述

Proposal

A dispatch rule for ADF: a task may run unattended for a long period only if it has (a) a machine-checkable acceptance criterion and (b) a control run on a case with a known answer, executed through the same pipeline before the real run. Tasks without both stay attended or tightly bounded (open-ended refactors, issue triage).

Why

Anthropic's nine-loop computation ran overnight on nothing but "keep going" prompts and produced a correct frontier result. Our runaway-loop failures have the same shape and the opposite outcome. The difference was not the model. The task carried its own oracle:

  • an eight-loop control run, checked against the published result;
  • exact arithmetic repeated modulo three primes;
  • two representations cross-checked on all 107,053 nonzero coefficients;
  • an independent group reproducing part of the result.

The loop detector should treat "long and making verifiable progress" differently from "long and repeating itself". A passing control run plus a checkable criterion is what makes that distinction possible.

Tasks

  1. Add an acceptance field (the command or check) and a control field (a known-answer case) to the task and agent definitions used for long or unattended dispatch.
  2. Spawner: refuse unattended mode when either field is missing, or when the control run fails.
  3. Loop detection (#3080): use progress against the acceptance check as a signal that a long run is still productive.

Acceptance

  • An unattended dispatch without both fields is rejected, with a clear message.
  • A deliberately broken pipeline is caught by its control run before the real task starts.

Source

https://www.anthropic.com/research/yes-claude-can-do-nine-loops ; result page https://smsharma.io/cosmic-nine-loops/


Mirror of Gitea terraphim/terraphim-ai# (source of truth).

主要语言
Rust
星标
65
派生
5
平均合并
1 小时
30 天内合并 PR
3

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

terraphim/terraphim-ai 的其他 Issue

查看 terraphim/terraphim-ai 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。