[bug] System prompt points at two rules in DA_IDENTITY.md that a principal-written…
Los mantenedores suelen responder en 5 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 52/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- documentation, tooling
Línea de trabajo
Start with LIFEOS/LIFEOS_SYSTEM_PROMPT.md and LIFEOS/TOOLS/DocCheck.ts, then inspect the referenced DA_IDENTITY.md sections and DocCheck’s existing path-reference checks. Confirm whether the cited rules and section anchors are present in the target documents. Done means the system prompt’s rule references match their sources and DocCheck reports missing section headings.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What happened
the system prompt cites rules in DA_IDENTITY.md (bolded lead-in ban, operative five-check) that a principal-written DA_IDENTITY does not contain, and DocCheck checks only paths, not section anchors
Summary
LIFEOS/LIFEOS_SYSTEM_PROMPT.md (v4.4.3, LifeOS 8.761.0) delegates two rules to DA_IDENTITY.md, a file the principal writes:
- Format Rules, "Enrich the text so it scans": "never a bolded lead-in on a bullet, which
DA_IDENTITY.mdbans". - The Voice paragraph: "the operative five-check and full voice contract live in
DA_IDENTITY.md§ Writing Style".
On my install the principal-written DA_IDENTITY.md has a Writing Style section but contains neither a bolded-lead-in ban nor a five-check. So the system prompt states as fact a rule that does not exist where it says it does: the model either follows a ban nobody wrote, or looks for a five-check that is not there. Every install whose principal rewrote DA_IDENTITY.md is in the same state. (The pre-emit check that does exist lives in the Writing Style backstop reference file, which the same sentence names as the backstop.)
Two suggestions:
- Doctrine should not rely on content in a user-owned file. Either state the rule in the system prompt itself ("never a bolded lead-in on a bullet") or point at a system-owned file, and keep DA_IDENTITY.md as voice only. The system prompt already does this well elsewhere ("pointer only" for Verification, "define nothing" for Permission Boundaries).
- Extend DocCheck to verify § anchors.
LIFEOS/TOOLS/DocCheck.tsextracts path references and checks the file exists. A reference of the form`FILE` § Sectionpasses even when the section is missing. Checking that the named heading exists in the target file would have caught both of these, and the same pattern in other docs.
Found by a coherence pass over the always-loaded doctrine files. Locally I replaced both citations with the rule itself and a pointer to the backstop's pre-emit check.
Details
- Kind: bug
- LifeOS version: 8.761.0
Filed with the LifeOS /feedback command. The reporter approved this exact text before it was sent; paths, secrets and personal details were stripped locally.
- Lenguaje dominante
- TypeScript
- Estrellas
- 19.9k
- Forks
- 2.5k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de danielmiessler/LifeOS
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
danielmiessler/LifeOS#2894 ·
Los mantenedores suelen responder en 5 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
danielmiessler/LifeOS#2891 ·
Los mantenedores suelen responder en 5 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
danielmiessler/LifeOS#2888 ·
Los mantenedores suelen responder en 5 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
danielmiessler/LifeOS#2886 ·
Los mantenedores suelen responder en 5 días
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
danielmiessler/LifeOS#2848 ·
Los mantenedores suelen responder en 5 días
Todos los issues de danielmiessler/LifeOS
Issues similares
-
ready-for-agent
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
LucasSantana-Dev/Lucky#3257 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
XiaomiMiMo/MiMo-Code#2849 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
enhancement frontend good first issue help wanted testing-infrastructure
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 2 días
-
enhancement follow-up
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
obsidian-tasks-group/obsidian-tasks#4155 ·
Los mantenedores suelen responder en 1 día