Concept Contrast Fable

Low-rank adaptation and low-rank adaptation: two ID cards for the same term

Conclusion first:A common awkward situation in technical documentation: in the same proposal, the first half says LoRA, the second half says low-rank adaptation (LoRA), the procurement list says Low-Rank Adaptation, and the contract appendix says LoRA (Low-Rank Adaptation). Readers and reviewers repeatedly check whether these are one thing or two. Different names have no impact on technical implementation, but they significantly affect procurement pricing, compliance audits, and version alignment of interface documentation—especially when different vendors use different wording in their quotes.

A common awkward situation in technical documentation: in the same proposal, the first half says LoRA, the second half says low-rank adaptation (LoRA), the procurement list says Low-Rank Adaptation, and the contract appendix says LoRA (Low-Rank Adaptation). Readers and reviewers repeatedly check whether these are one thing or two. Different names have no impact on technical implementation, but they significantly affect procurement pricing, compliance audits, and version alignment of interface documentation—especially when different vendors use different wording in their quotes.

Fable

Kiwi and kiwifruit in the fruit market

There is an unwritten rule in the fruit wholesale market: imported from New Zealand is called kiwifruit, domestic is called mihoutao. The botanical name is the same, the flesh color differs slightly, but once cut open it is the same thing. Veteran buyers all know this rule—when placing orders, just write the name according to origin. Until one day, a chain supermarket's supply chain system launched automatic price comparison.

The system scanned Supplier A's quote: kiwi fruit, 28 yuan per kilogram. It then scanned Supplier B's quote: kiwi (New Zealand variety), 26 yuan per kilogram. The system judged these to be two different products and recommended Supplier B's kiwi to the procurement manager—because it was cheaper. But Supplier B's product was actually domestic, not the New Zealand variety, with completely different taste and shelf life.

Where did the problem lie? It lay in the lack of a unified naming convention. Supplier A named strictly by origin, Supplier B named by variety with a parenthetical note, and the system did not understand the actual meaning of the five characters "New Zealand variety," matching only literally. Automated price comparison bypassed a judgment that should not have been bypassed: are these two quoted lines talking about the same thing?

The market supervision department later did something: it listed a comparison table of all combinations in the market where the same item had different names—cherries and cherries, pineapples and pineapples, kiwifruit and kiwifruit—and required all suppliers to mark both the standard product name and the common name when quoting. The system added a mapping layer, and during purchasing it first classified all names under standard product names, then compared prices.

The wholesale market later posted a list of different names for the same goods at the checkout counter. Kiwifruit, mihoutao, New Zealand varieties, domestic varieties — which are the same thing, and which merely have similar names but are different goods — all written on one sheet. When suppliers quote prices, they must also write both the standard product name and the common name; they cannot rely on a single local expression and leave the buyer guessing.

A chain store was once stuck for three days because of this. The purchase order said kiwi, the warehouse intake form said mihoutao, and the finance receipt said imported green fruit. Placed together, the auditor thought three batches of goods had been bought. In the end, only a certificate from the market supervision office allowed release. The goods were not wrong, but the trust cost caused by messy names was very real.

From then on, the procurement manager built a glossary for all fruits. On first mention, write the standard name, the common name and the origin; afterward, use the standard name consistently. This rule was not complicated, yet it saved countless explanations: the same thing can have many names, but in external transactions there must be one stable set of applicable definitions and criteria.

LoRA / low-rank adaptation

Abbreviation for Low-Rank Adaptation, a parameter-efficient fine-tuning technique that adapts a pretrained model to a task by injecting low-rank decomposition matrices into its weight matrices, greatly reducing the number of trainable parameters.

Low-Rank Adaptation (LoRA)

It refers to the same technology as LoRA, usually the full name for Low-Rank Adaptation in Chinese-language contexts or formal documents, with no difference in technical implementation.

Story Mapping

Kiwifruit and mihoutao: different names for the same item, with price differences caused by different origins
An automated price comparison system treats kiwifruit as different products: procurement decision bias caused by inconsistent naming
A noun glossary lets price comparison classify before comparing: the terminology mapping layer in documentation
Blocked at acceptance because LoRA and Low-Rank Adaptation didn't match: the compliance communication cost of different names for the same thing

Applied to business document management

When presenting a proposal or contract to a client, create a terminology reference table at the beginning of the document, listing the English full name, abbreviation, and Chinese translation of each technical term. Use one primary name consistently across all sections, and mark other forms as “i.e., xxx” when they first appear. This rule is especially critical for different names for the same thing such as LoRA/Low-Rank Adaptation/low-rank adaptation, and can prevent repeated challenges about inconsistent terminology during procurement review and compliance review.

Low-Rank Adaptation Low-Rank Adaptation