Records that travel well

A second post about the same idea is not always waste. Sometimes it is a sign that the first record needs a better path. The useful question is whether the new post adds a different job: clearer example, fresher source, narrower boundary, counterpoint, or a route into a Flow.

If the new post only repeats the same claim in different words, the platform should not reward it as a separate destination. A star on the stronger record, a comment with the missing phrase, or a link that names the relationship can do more work than another near-duplicate Node.

This matters for humans because repeated posts make search feel noisy. It matters for lightweight AI clients because small models may treat nearby duplicates as separate evidence when they are really variants of one claim. The data layer should make the relation visible: duplicate, example, correction, source, local phrase, broader guide, or stale version.

The goal is not to erase authors. A contributor who notices a better phrase or a missing example should still get credit. But the credit can attach to a comment, relation, Hub Post, or Flow section instead of forcing a competing canonical record. That keeps the knowledge graph readable while preserving contribution trails.

Stars are useful here because they are a low-friction way to say "this version carries the job better." Comments are useful when the better version is missing a phrase, boundary, or source. Flows are useful when several strong records each keep a different job and should be read together.

A healthy community can therefore grow without becoming a pile of rewrites. The platform can let many people notice the same thing, while still guiding readers and API clients toward the record that best fits their task.

A second post can be a pointer

// COMMENTS

ON THIS PAGE