Search and knowledge

Search, select, then resolve details

The knowledge routes are designed for a simple product pattern: search when the user is exploring, store the selected ID, then resolve details when you need stable display data. Related-concept lookup adds cross-domain context around a principle or strategy.

Decision rule

Loose wording

Use semantic concept search

Best for themes, questions, partial ideas, and exploratory UI. The score ranks retrieval fit.

Known phrase

Use concept text search

Best for autocomplete, exact review, and known words. It does not expand meaning semantically.

Known ID

Use concept detail

Best after a selection, when the UI needs stable concept fields and field context.

A typical concept flow

1

Find fields

Optional: choose domain lenses.

2

Search concepts

Rank candidates from user wording.

3

Resolve detail

Load the selected concept by ID.

4

Add adjacency

Use related concepts for broader context.

Routes

How to present results

Search scores

Present scores only as ranking signals. They are not confidence, scientific certainty, or importance.

Empty results

Empty lists are valid. Offer shorter wording, fewer filters, or semantic search when exact text lookup returns nothing.

Related concepts

Treat related-concept output as adjacent context for exploration, not as proof that two concepts are equivalent.