The neighbourhood panel (note: Neighbourhood map) of a page lists neighbour (42 passages, no note) types (note: Type) in a priority (3 passages, no note) order declared per type in the profile (note: Profile): operations (note: Operation) first on an API (note: API), accessed objects (28 passages, no note) on a screen (note: Screen), what it applies to on a rule (note: Rule). Every displayed neighbour carries the rank (6 passages, no note) of its type; unlisted types and keyword pages (note: Keyword) share the last rank, confidence (note: Confidence) decides within a group (23 passages, no note), and the panel (97 passages, no note) is truncated after this ordering. A type without a declaration (3 passages, no note) keeps the order by decreasing (4 passages, no note) confidence. The order is profile data, never a condition in a template (22 passages, no note): the panel renders (24 passages, no note) the list as received and separates the groups by rank alone.
Type-driven neighbour order
Decision · Acceptedspecs/decisions/inference/type-driven-neighbour-order
Properties
- Status
- Accepted
- Decided on
2 keys: the status and the date are authoritative.
See the neighbourhood map6 pages6Neighbourhood mapType-driven neighbour order
Neighbourhood map Type-driven neighbour order
Distance1 hop
17 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- Entity pageScreenaffects1
- Neighbourhood mapScreenaffects1
- Keyword pageScreenaffects1
- Build pipelineProcessaffects1
- ModelBusiness objectaffects1
- BuildBusiness objectaffects1
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.