okhp3-notion-search-strategy

原文涵盖的主题

• okhp3-notion-search-strategy
• Scope
• Choosing a search backend
• Filters and plan gating
• Rate limit discipline
• Result triage
• Output contract
• Tooling

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Finds content by keyword or topic when the user does not already know where it lives. Always load okhp3-notion-core first. | In scope | Out of scope | |---|---| | Keyword/semantic search across Notion and connected apps, filter selection, plan-gate routing | Filtering and sorting rows in a known data source (okhp3-notion-query). Enumerating everything that exists regardless of a search term (a governance-tier skill) | Workspace search: faster, Notion-only, supports exact filters and non-relevance sorting (by lastedited or created). AI search: semantic, includes connected apps (Slack, Google Drive, GitHub, Jira, Microsoft Teams, SharePoint, OneDrive, Linear). Requires Notion AI on the workspace. If the caller does not specify a backend, the default auto-selects AI search when available, otherwise workspace search. Only force a specific mode when the task specifically needs one: force workspace search for exact-filter or non-relevance-sort needs (these cannot combine with AI search), or force AI search when the target is explicitly in a connected app. Available on every plan: location scoping (page, data source, or single teamspa

这里只展示节选，请以完整原文和当前要求为准。