okhp3-notion-core

原文涵盖的主题

• okhp3-notion-core
• Scope
• Step 1: Detect the available surface
• Step 2: Read the capability map before calling anything
• Step 3: Pin the API version
• Step 4: The mandatory database-to-data-source resolution rule
• Step 5: Apply the error taxonomy
• Portability and privacy contract

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Foundation for the entire okhp3-notion- family. Every Notion task starts here, even when it ends in a domain skill. This mirrors how okhp3-mermaid-core anchors the Mermaid family: core carries the cross-cutting contract, domain skills carry the vocabulary. This skill performs no Notion operation. It decides how to talk to Notion, then hands off. If you find yourself about to call a Notion tool from inside this skill, stop and route to the sibling that owns that object type. | In scope | Out of scope | |---|---| | Surface detection, capability-map reading, API version pinning, database/data-source resolution rule, error taxonomy, portability fallback | Any actual page read/write, row read/write, search, query, or delete. Those belong to Tier 1+ siblings | Notion is reachable through three incompatible surfaces. A user's environment may offer one, two, or all three. Check in this order and record which is active: 1. Hosted Notion MCP (notion- tool prefix, e.g. notion-search, notion-fetch, notion-create-pages). OAuth session, acts as the connected human user's full permissions. 2. REST-shaped MCP or direct REST (API- tool prefix o

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