View source for Bot:Guide/search

This page provides the bot with guidance on how to interpret page titles from user requests and how to search the wiki when an exact match is not found. The bot reads this page automatically at startup and on every polling cycle.

{{Section separator}}

== Naming convention ==

Pages on this wiki follow a structured naming convention using namespaces, subpages, and natural language titles.

'''Namespaces''' are prefixed before a colon. Common namespaces include:
* <code>Web:</code> — web-sourced content, organised by company and topic (e.g. <code>Web:AXA/results/FY25/Press release summary</code>)
* <code>Definition:</code> — glossary and terminology entries (e.g. <code>Definition:Combined ratio</code>)
* <code>Bot:</code> — bot configuration and service logs (internal use only)
* <code>Prompt:</code> — prompt templates (internal use only)
* Main namespace — pages without a prefix (e.g. <code>Thomas Buberl</code>, <code>Cyber insurtech MGAs and underwriting agencies</code>)

'''Subpages''' are separated by forward slashes <code>/</code>. They represent a hierarchy within a namespace or page. For example:
* <code>Web:AXA/results/FY25/Press release summary</code> — the page "Press release summary" is a subpage under <code>Web:AXA/results/FY25</code>

'''Interpreting user requests:'''
* When a user says "page X in Namespace:Path", the full title is <code>Namespace:Path/X</code>
* When a user says "page X in Path", look for <code>Path/X</code> or identify the most likely namespace
* When a user gives a plain name like "Thomas Buberl", the page is in the main namespace
* Page titles are case-sensitive for the first character after the namespace; subsequent words follow the title as stored on the wiki

'''Examples:'''
* "press release summary in Web:AXA/results/FY25" → <code>Web:AXA/results/FY25/Press release summary</code>
* "combined ratio in Definition" → <code>Definition:Combined ratio</code>
* "Thomas Buberl" → <code>Thomas Buberl</code>
* "the page FY25 results summary under Web:AXA" → <code>Web:AXA/FY25 results summary</code>

{{Section separator}}

== Intent routing ==

When the user's request implies a specific category of information,
the bot should prioritise searching within the corresponding path:

{| class="wikitable"
! User intent !! Path !! Examples
|-
| Contact information, team members, org structure || <code>Internal:Teams/</code> || "who is in Group tax", "contact for corporate finance"
|-
| Training materials, courses, learning || <code>Internal:Training/</code> || "the training on cyber risk", "onboarding course"
|-
| AXA financial results || <code>Web:AXA/results/</code> || "FY25 press release", "AXA half-year results"
|-
| Glossary, definitions, terminology || <code>Definition:</code> || "what is combined ratio", "define loss ratio"
|}

This table is a hint, not a hard rule. If no result is found in the
suggested path, the bot should fall back to a full wiki search.

{{Section separator}}

== Search ==

When the bot cannot find an exact match for a requested page title, it performs a search across the wiki.

'''Search scope:'''
* The bot searches across '''all''' namespaces on the wiki
* The following namespaces are '''excluded''' from search results:
** <code>Bot:</code> (namespace ID 3000) — internal bot configuration and logs
** <code>Prompt:</code> (namespace ID 4002) — internal prompt templates
* These namespaces are excluded because they contain internal operational content that users would never want as a PDF

'''Search results:'''
* The bot retrieves the top 10 candidate pages from the search results
* An AI model then evaluates each candidate against the user's original request and selects the best match
* If no candidate is relevant, the bot reports that the page could not be found
* If a match is found but is not exact, the bot explains clearly in its reply that the attached PDF is the closest match, not the exact page requested

'''Confidence levels:'''
* '''High''' — the candidate clearly corresponds to the user's request (e.g. minor spelling difference or capitalisation mismatch)
* '''Medium''' — the candidate is likely correct but there is some ambiguity
* '''Low''' — the candidate is a stretch; the bot attaches it but warns the user to verify