okhp3-notion-domain-filing

Topics in the source

• okhp3-notion-domain-filing
• Scope
• Configure once, verify each run
• Filing pass
• 1. Establish ownership and discover a bounded batch
• 2. Verify purpose and choose a home
• 3. Plan identity, index, and verification before moving
• 4. Move natively, verify, then reconcile the index

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Give each original one physical home within the owner's verified domain roots. Maintain its catalog entry and related navigation without turning filing into content editing. This package contains no workspace destinations or scheduler. Use the current session's authorization, including an explicitly authorized recurring scope. Prepare a read-only plan before any approval still needed; do not repeatedly request permission already supplied. An uncertain destination is a review item rather than a reason to guess or create a new hub. Load okhp3-notion-core first when available for live capability mapping, then okhp3-notion-identity-resolution and okhp3-notion-limits-and-retry when their operations are needed. Without those packages, inspect the connection's actual read, search, native move, schema, query, and update tools before proceeding. If native moves are unavailable, report the proposed moves; never emulate one by copying a body into a new page and archiving the original. Read references/runtime-contract.md during setup, on a configuration change, or when resuming an interrupted run. Obtain the canonical discovery root, appro

This is an excerpt. Refer to the complete source and its current requirements.