Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#968 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
ai-infra-agents

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
Rust
Sterne
65
Forks
5
Ø Merge
1 Std. 17 Min.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus terraphim/terraphim-ai

Alle Issues in terraphim/terraphim-ai

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.