Synchronization

How Notion content becomes searchable context.

Vercel invokes GET /cron/sync every six hours. POST /v1/sync triggers the same job manually.

Each resource follows an incremental flow:

1. Read current published Notion records.
2. Compare last_edited_time and content hash with stored records.
3. Fetch content and create embeddings only for changed records.
4. Upsert changed records.
5. Remove records no longer present in source database.

Database changes happen only after new content and embeddings are ready. Failed records retain their last searchable version.