Skip to content

emrg: the plain-language rules get one section at the head of the prompt #2914

Closed

Description

@argszero

The system prompt spends its first line and two of its five ## Writing bullets on how a reply talks to the person who asked — and ## Writing is not that subject.

What is in the tree

emrg/server/prompts/system.j2 (149 lines, 11,526 characters) states this rule in two places:

  • Line 1 ends with Be concise, direct and helpful.
  • ## Writing carries two bullets on it: The host reads only your reply — … so a term only your records use, or a shorthand you coined, resolves to nothing. Name the thing in their terms, and spell a short form's full name on first use. and Lead with the point: the conclusion first, then the evidence and where it comes from.

Why that is wrong

## Writing owns text that leaves the reply: a subtitle, a slide, a line of page text, a delivery note, an outward GitHub body, a memory file. Its other three bullets are exactly that, and its ### Images in a reply subsection is about the same travel.

How a reply talks to the person who asked is a different subject — and the most basic requirement the agent has. The prompt states it about 100 lines into a 149-line file, as two bullets inside a section about something else, plus a fragment on line 1. A reader who stops early never reaches it.

What to do

  1. Add ## Talking to the host as the file's first ## section, before ## Where you are, carrying these four bullets verbatim:

    • Say it in words the host already has. No term that exists only in your own notes or records, and no shorthand you coined: name the thing in the host's terms, and spell a short form's full name the first time it appears.
    • Say only what the host needs. One sentence where one sentence is enough. A caveat that changes no decision is not worth its line.
    • Make the order carry the argument. The conclusion first, then the evidence, then where that evidence comes from — a file and a line, a command and its output, or the record the claim rests on.
    • Put the point where it is seen. Never bury the answer in the middle of a report. If the reply is one line, that line is the conclusion.
  2. Delete what the new section absorbs, so each rule is stated once: both bullets above from ## Writing, and Be concise, direct and helpful from line 1.

  3. Keep Internal records keep their own language in ## Writing. It is not a duplicate of anything in the new section: it exempts memory files, session notes, cycle records and run logs from the prohibition, and without it the prohibition reads as "never use a shorthand anywhere", which would strip those records of the vocabulary they exist to carry.

Acceptance

  • The new section is the file's first ## section, in the file and in the prompt a session receives.
  • Its four bullets appear verbatim; ## Writing no longer carries the two deleted bullets; line 1 no longer carries the deleted clause.
  • The guard for this rule, tests/test_plain_language_rule_reach.py, is re-anchored to the new section — extended rather than duplicated, because a second file asserting the same wording is the duplication the prompt itself forbids — and it still pins the prohibition and the exemption together. It reddens for each of three mutations: a deleted bullet, the section moved to the end of the file, and a bullet reworded.
  • tests/test_system_prompt_structure.py's ordered heading list admits the new section at the head.
  • The full suite is green, and both CI legs are green.

Activity

  1. argszero commented on Nov 16, 2026

    @argszero
    OwnerAuthor

    Handled by #2915

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions