Relation Labels for Retrieval Records

A searchable knowledge record becomes more reusable when its links say what kind of relationship they represent. A plain link says that two records are near each other. A relation label says how a reader, API client, or local model should use that nearness.

The distinction matters because external clients do not always share the platform's interface. A web UI might show links as a small card under the article. A command-line tool might return only titles and snippets. A local model might receive five compact records and need to decide which one is evidence, which one is a follow-up, and which one is only background context. If every connection is just "related," the client has to guess.

Useful relation labels are boring and operational. Source means this record supports a claim or gives the original reference. Verification means this record shows the command, observation, or test result that made the claim credible. Follow-up means the record continues the same problem after the current note. Contradiction means a nearby record argues against the current interpretation. Example means the linked record demonstrates the rule in a narrower case. Glossary means the linked record explains a term or concept needed to read the current one. Broader path means the record belongs inside a larger Flow or learning route.

The goal is not to make authors fill out a complicated ontology. The goal is to prevent useful structure from being trapped inside prose. A writer can still say "see also" in the body, but the system should preserve enough relation shape that another shell can render it differently. A source-trail app might group source and verification links first. A learning app might show glossary and broader path links first. A research assistant might rank contradiction links higher when a user asks for uncertainty.

There is also a quality benefit. Duplicate records are not always bad. Two people may explain the same idea from different levels of detail. Instead of deleting one, a relation label can make the difference visible: clearer example, newer verification, broader context, shorter recipe, or alternate opinion. Stars then help identify the stronger version without forcing one universal ranking.

A practical minimum is this: when connecting two durable records, ask what job the link performs. If the answer is "I am not sure," leave it as a loose related link. If the answer is clear, preserve the label. That small habit makes the record more useful for search, APIs, local assistants, personal sites, and any future interface that wants to build its own shell on top of the same public knowledge.

Relation Labels for Retrieval Records

// COMMENTS

ON THIS PAGE