Repository navigation
Description
What happens
emrg/server/self_media_prompt.md tells a round what a product must contain (§3), how to publish it (§4) and what its archive must record (§5). It never says what to do with a field the round cannot source. Two installations running the same template therefore ship two different products from the same instruction: one writes a placeholder into the product ("not read", "unknown"), the other leaves the field out and records the gap somewhere else — and nothing in the template says which of those is right.
The nearest rule is Forbidden item 5, never fill a missing value with an invented one — report it, never guess. That settles invention. It does not say where the report goes, so it does not settle what the reader of the product sees.
Where it was observed
emrg/server/self_media_prompt.md, read in full (178 lines):
- §3 (lines 83–97) governs the draft's shape and says nothing about a field's provenance.
- §5's readings table (lines 137–146) has a fixed field list —
topic_source,structure,word_count,trend_data,publish,platform/date/task— and no field for what could not be read. - Forbidden (line 174) forbids inventing a value.
An installation's own config.extra_prompt can carry the rule (this one does, at length), which is the point: a general rule is living in one installation's private block, and the template that every installation renders has no counterpart.
Why it matters
A product is read by someone who is not the round and cannot see the archive. Two failures come from the gap:
- A placeholder in the product spends the reader's attention on the absence. A card, a post or a summary that prints "not read" for four fields is mostly a list of what the round failed to do. The rule the template lacks is that an unsourced field is absent from the product, and the absence belongs in the archive's readings, where the host reads it.
- A property inferred from a correlated signal is written as if it were stated. The template has no rule that a fact about a third party comes only from that person's own statement. An avatar, a name, a tone of voice, a timezone or a follow list are all correlated with such a property and none of them is a source; a product that writes one of them as fact cannot be corrected afterwards, because the error reads exactly like the sourced fields beside it.
What the fix must satisfy
Rewrite — do not append — inside the sections that already own these subjects:
- §3 gains one rule: a field carries the source of its value, and a field whose source the round cannot name does not appear in the product.
- §5 gains one row in the readings table for what could not be read, with the reason, so the absence has one home and it is the archive.
- The subject-of-the-product half: where the product describes a third party, a property is written only from that person's own statement; a correlated signal is not a source. This states what a source is; it does not add a list of fields, and it names no platform.
- No contradiction is left standing: Forbidden item 5 keeps its subject (never invent) and the new sentences say where the absence goes, so the two do not read as two answers.
Acceptance
emrg/server/self_media_prompt.mdstates all three: provenance for a field, absence recorded in §5's readings block, and a source is a statement rather than a correlated signal.- The change is prose only, and adds no test that pins the sentences' wording — a guard on a sentence's literal text answers "the file did not change", not "the rule is still there".
- A reading of the rendered template (the project's own prompt-template test) still passes with and without an
extra_prompt.
Activity
pm25coder commentedon Nov 14, 2026
Handled by #2902