Protected roles and org integrity (no self-termination of the last lead; loop-safe attribution)

Abierto
#162 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

The issue names no implementation files or tests; start by tracing agent termination, event attribution and wake rules, plus task reopening behavior, and inspect related issues #117, #145, #1334, #3817 and #3980. Add tests for protected lead/capability removal, self-authored comments not waking their author, and human-only reopening; done means all three rules are enforced and the attempted lead termination produces an Inbox note.

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

Descripción

area:agents area:security needs-triage p1 type:feature

Part of #117 · Part of #145 · beat-Paperclip spec id E12

  • Priority: p1
  • Labels: type:feature, area:agents, area:security
  • Relates to: #117 (#128), #145
  • Scope: In Paperclip, the CEO "deleted itself" and took hiring rights with it (#1334). Agent comments are attributed to the user and re-trigger loops (#3817), and agent edits reopen done tasks (#3980). Muster rules:
    • Lead roles are protected: they can't be terminated or paused by an agent, and the last holder of a capability can't be removed.
    • Every event carries an actor from the Ledger, and wake rules ignore self-caused events.
    • Only a human can reopen a done task.
  • Acceptance:
    • An agent's attempt to terminate the lead is refused with an Inbox note.
    • A self-authored comment never wakes its author.
    • Tests cover each rule.

Source: Paperclip issue/discussion research (docs, GitHub issues, live instance).

Lenguaje dominante
TypeScript
Estrellas
3
Forks
0
Merge medio
17 h 33 min
PR fusionados (30 d)
163

Preparar el entorno

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 musterhq/muster-code

Todos los issues de musterhq/muster-code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.