Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#968 1 comentário 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
rust
Domínio
ai-infra-agents

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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).

Linguagem predominante
Rust
Estrelas
65
Forks
5
Merge médio
1h 17min
PRs com merge (30d)
2

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de terraphim/terraphim-ai

Todas as issues de terraphim/terraphim-ai

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.