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

Decide whether a coordinator may lift a headless worker's refusal (the trust boundary #68 defers)

Abierto
  • ¿Algo no está bien?
#142 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
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
typescript
Área
authorization, security

Línea de trabajo

Start with the refusal key resolution at index.ts:3203, liftRefusals at index.ts:3262, and the dialog-approval and headless checks at index.ts:4302 and index.ts:4333. Decide and document the trust-boundary policy, then add tests covering coordinator authorization, critical refusals, and attribution of both identities in decisions.jsonl. Done means the chosen constraints hold and the agent-on-behalf-of-user behavior is documented.

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

Descripción

enhancement ready-for-human

Split from #68 by your decision there: the mechanical half (narrowing the refusal key) is agent work on that issue, and this is the trust boundary it deliberately does not touch.

The gap. A headless worker cannot lift a refusal. liftRefusals (index.ts:3262) runs at exactly one call site, inside the dialog-approval handler (index.ts:4333), and that handler is only reachable when ctx.hasUI — index.ts:4302 collapses every headless hit into a block before any lift path. A refusal a coordinator considers wrong therefore stays for the whole session.

Why it is a design call and not a fix. Building the channel means answering who may lift a refusal taken on another agent's command, whether an agent may approve on a user's behalf, and whether a critical refusal is ever liftable. Those are the same questions the persistent-grant surface answers for a human, asked about a machine, and the answer decides how much of the prod-secrets posture moves.

Options as presented.

  1. A registered tool a coordinator may call, with headless coordinators rejected by construction, critical refusals permanently unliftable, and the hop recorded in decisions.jsonl with both identities. Cost: an agent-to-agent approval path exists at all.
  2. Lift only with a human-issued token in the environment, so an unattended session still cannot lift. Cost: it is a human approval with extra steps in the common case.
  3. Leave it unliftable, documented with the reason. Cost: a wedged headless worker is restart-only.

Acceptance, whichever is chosen: the chosen constraints hold under test (a headless coordinator is rejected or accepted as specified; a critical refusal cannot be lifted by any path); every lift is attributable in the log with the lifting identity and the original refuser; the docs state what an agent may do on another agent's behalf.

Related: #68 (key narrowing), and the refusal store's key resolution at index.ts:3203.

Lenguaje dominante
TypeScript
Estrellas
0
Forks
1
Merge medio
2 h 10 min
PR fusionados (30 d)
64

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 STRML/omp-classifier

Todos los issues de STRML/omp-classifier

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.