Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Keeper triages results with a decision model

Abierto
  • ¿Algo no está bien?
#64 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp
Área
ai, backend

Línea de trabajo

Start with parent issue #21 and the prerequisite #63, then trace the existing triage flow, Scout registration, run recording, model gate, settings path, and research note handling. The issue specifies unit, handler, client, and TestWiki integration tests; done means the Keeper replaces Scout triage, its calls and verdicts appear in Runs, kept results produce notes with quotes, and the listed documentation and settings are updated.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement ready-for-agent

Parent

#21

What to build

The Keeper, a decision model served by llama-server's /v1/systemone, takes over judging fetched results from the Scout. It keeps or discards each result from probabilities, flags injection attempts and picks exact quotes. Kept results still become one research note per topic. Until the Clerk lands (next ticket), notes carry title, URL, kind and quotes without a summary, and the Scout is no longer run.

Acceptance criteria

  • A Keeper port (e.g. IKeeper) with a /v1/systemone client, configured with the model name on the shared llama-server (router mode) or its own endpoint, and generous timeouts; it is not an AIAgent
  • One call per fetched result: state = topic brief plus delimited fetched content; questions useful (noul), kind (choice with described options: release, announcement, discussion, tutorial, opinion, beginner question, spam, unrelated), injection (noul) and quotes (choice over the content's paragraphs, top three, length-capped in code)
  • Kept when useful ≥ Research:KeepThreshold and injection < Research:InjectionThreshold; the verdict stores the probabilities, kind and quotes; a discard's reason is derived in code
  • A failed or timed-out call leaves the result waiting for the next cycle; a page that could not be fetched is discarded without a call, as today
  • Each call is recorded as a run (Triage trigger, no tool calls) and shows on the Runs page with its probabilities
  • Calls go through the model gate ahead of Pleb runs and count against a per-cycle cap; the cycle is skipped when the model server is unhealthy
  • Research notes hold title, URL, kind and quotes per kept result, never page text; existing header, file naming and awaiting/completed moves unchanged
  • New settings and AppHost parameters (model, thresholds, cap) follow the usual path: AppHost, CD workflow env: with || 'default' fallbacks, scripts/setup-github.ps1
  • The Scout is no longer run by triage (its registration is removed in the Clerk ticket)
  • docs/ubiquitous-language.md gains Keeper; Verdict, Triage and Research note updated; README research section updated
  • Unit tests: threshold and injection rules, quote capping and derived reasons as pure policies; handler tests with a substituted Keeper cover keep, discard, injection, failure/resume and aggregation; the client tested with a substituted HttpMessageHandler
  • Integration test over TestWiki with a scripted Keeper drops the expected note in the inbox

Blocked by

  • #63
Lenguaje dominante
C#
Estrellas
0
Forks
0
Merge medio
40 min
PR fusionados (30 d)
47

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DigiBanks99/knowledge-base

Todos los issues de DigiBanks99/knowledge-base

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.