[bug] System prompt points at two rules in DA_IDENTITY.md that a principal-written…

Aperta
#2,783 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 5 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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:

  1. Format Rules, "Enrich the text so it scans": "never a bolded lead-in on a bullet, which DA_IDENTITY.md bans".
  2. 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.ts extracts path references and checks the file exists. A reference of the form `FILE` § Section passes 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.

Lingua principale
TypeScript
Stelle
19.9k
Fork
2.5k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di danielmiessler/LifeOS

Tutte le issue di danielmiessler/LifeOS

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.