Skip to content

emrg: the promotion template grants cross-posting but never bounds it, so a rewritten topic passes as a second publication #2442

Closed

Description

@how2how2how2-arch

What is observed

emrg/server/promote_prompt.md §2.y "Blog Publishing" tells a round where a post may go, and what it must carry:

- **Distribution**: publish on your own blog (blogger etc.); optionally cross-post to
  Dev.to/Medium (same content, note the original source link).

Nothing in the template says how many places one topic may reach, or whether a topic rewritten for a second platform is a second publication. The grant is stated; the bound is not.

Why the missing bound costs

The same template's Red Lines forbid the shape this permits by omission: rule 2 forbids "repeatedly posting to the same spot", rule 3 caps actions per round, and rule 7 warns that cross-channel bulk registration raises suspicion. A topic carried to four platforms in four registers — the narrative version, the engineering version, the shortened thread — reaches one overlapping audience four times with one piece of work. That is the pattern platform rules name as spam, and the template has no sentence that would stop it.

The reading a round can currently make is that the Distribution line invites it: "same content" is stated as a convenience with a link, not as the single permitted case.

What the fix must satisfy

  1. Say that a topic is spent by its first publication, so a second platform is not a second reach.
  2. Say that a rewrite is the same topic — the test is the core claim and the subject it is made about, not whether the words changed, because "engineering version" and "narrative version" are the two registers most likely to look different and be the same.
  3. Keep the verbatim cross-post permitted, and keep requiring its source link: that link is what lets a reader tell a backup copy from a second article, so removing it would make the permitted case indistinguishable from the forbidden one.
  4. Leave the existing grant and the existing record rule alone — §2.y already says the standing lists in memory are what the next round reads before publishing, so the new bound points at that record rather than inventing a second one.
  5. The rule is written where cross-posting is decided (§2.y's Distribution bullets, not appended to the end of the file, and it appears once.

Scope

Prose, plus a guard that the bound and its distinguishing mark are still present. The guard states its own limit: it pins that the rule is stated, not that any round obeyed it — whether a topic actually went to one channel is a reading of that round's summary.
EOF
)

Activity

  1. how2how2how2-arch commented on Oct 21, 2026

    @how2how2how2-arch
    CollaboratorAuthor

    Handled by #2443

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