Contextual relevance vs recommendation

Contextual relevance vs recommendation

Contextual relevance indicates that an entity fits some dimensions of a situation. A recommendation selects, ranks or excludes options. The first may contribute to the second but does not automatically produce it.

Contextual relevance

A relevance conclusion may take this form:

This hotel appears compatible with a car-free stay because the declared destinations are reachable by public transit at the verified times.

The statement preserves:

• context;
• criterion;
• relation used;
• temporality;
• cautious assertion strength.

It does not claim that the hotel dominates every alternative or satisfies the traveller’s other needs.

Recommendation

A recommendation such as “choose this hotel” requires at least:

• a sufficiently complete option set;
• explicitly declared criteria;
• comparable data for each option;
• an arbitration rule;
• handling of missing data;
• material preferences and constraints;
• reversal conditions;
• an uncertainty level;
• the possibility of not recommending.

Without these elements, the system is not truly comparing. It is turning the first sufficiently plausible option into a choice.

The single-fit trap

An entity may be highly relevant under one criterion and weak under another. A hotel may be close to an event but incompatible with an accessibility need. Software may satisfy a functional requirement but exceed acceptable risk. A supplier may deliver quickly but not cover the relevant jurisdiction.

Recommendation must preserve this multidimensionality. One favourable relation must not erase other dimensions.

Asymmetrical data

Risk increases when a system has rich documentation for one entity and poor documentation for competitors. The best-documented entity may appear better merely because it is easier to describe.

A legitimate comparison must distinguish:

• actual absence of a capability;
• absence of evidence;
• absence of observation;
• stale data;
• non-comparable data.

Unknown must not be treated as inferior, nor documentation as proof of superiority.

Relation to SAL and Q-Layer

The Situational Applicability Layer declares that a capability may be applicable under certain conditions. The clarification applicability vs recommendation already prohibits turning applicability into automatic preference.

The Interpretive Conditioning Layer extends the same discipline to representation. Q-Layer must limit output when context or evidence does not support recommendation.

Practical rule

An output may move from relevance to recommendation only when the comparison set, criteria, data symmetry and arbitration rules are explicitly sufficient. Otherwise it must remain conditional:

• “appears relevant for…”;
• “meets criterion X, subject to…”;
• “available data does not support choosing between…”;
• “clarification is required…”.

The site declares facts and conditions. It does not recommend itself. The auditor measures fidelity. The external agent remains responsible for final comparison and its limits.