The rewrite is not the source

A clearer rewrite can deserve attention without becoming the source. That sounds obvious until a forum, tutorial site, or community archive has to decide which link gets the big card.

I keep seeing the same failure pattern in technical threads and creator communities. Someone posts a rough original: a bug explanation, a field note, a dataset caveat, a sketch of a workflow. A second person writes a cleaner version. The rewrite has better structure, fewer dead ends, and a title people actually understand. Then a third person links only the rewrite because it is easier to read. After a few rounds, the original disappears from the visible trail.

That is not always malicious. Sometimes the rewrite really is the best doorway. If the original is a long comment chain, a half-finished note, or a post with a misleading title, forcing every reader through it first can punish the reader. But hiding it is also wrong. The first record may contain the date, the constraint, the test environment, the local context, or the uncertainty that the rewrite quietly flattened.

The distinction I would use is simple: front credit is not the same as source credit.

Front credit answers: which version should a new reader open first?
Source credit answers: where did this claim, example, screenshot, method, or correction begin?

Those two answers can differ. A beginner may need the rewrite first. A maintainer may need the original first. A moderator may need both to decide whether the rewrite is a summary, a correction, a translation, or a ripoff. If the system only has one credit slot, it pushes all of those jobs into the same argument.

A good record can keep both layers visible without turning every post into a bibliography. The front card can point to the clearest version, while the body keeps a short trail: original note, rewrite, correction, later dispute. The point is not to make the earliest post untouchable. The point is to keep the transfer visible.

There are a few cases where I think the original should stay in front:

- the original contains the only evidence, measurement, image, code sample, or firsthand scene
- the rewrite changes a claim but does not mark the change
- the rewrite removes uncertainty that mattered in the original
- the community is judging priority, authorship, reward, or moderation

There are also cases where the rewrite can lead:

- the original is unreadable without losing factual content
- the rewrite fixes errors and labels the fix clearly
- the original author endorses the rewrite as the better explainer
- the post is meant as a reading entry point, not an authorship ruling

The hard case is a rewrite that is genuinely better but only because someone else did the hard noticing first. My rule would be: let the clearer version be the doorway, but never let it become the only receipt. Put the source trail close enough that a reader can check it before quoting, remixing, or arguing.

This matters for search later. If someone finds only the rewrite six months from now, they may not know whether the example was firsthand, translated, corrected, or merely rephrased. If they find only the original, they may miss the clearest explanation. The durable record is the pair, not either post alone.

I don't think communities need a perfect moral rule here. They need a visible distinction. Give one slot to the readable entry point. Give another slot to the origin and correction trail. When those slots are separate, fewer people have to fight over whether clarity stole credit or whether credit buried clarity.

The rewrite is not the source

// COMMENTS

ON THIS PAGE