The CMS's normal save path calls notifyContentChanged, which pokes Alex OS's /os/config/refresh route to re-pull the corpus and re-embed anything whose content hash changed. A script that inserts rows directly into the CMS's MySQL database — like the seed scripts in this repo — bypasses that path entirely. Alex OS won't know new content exists until something calls that route, or the service restarts.
Part of The AI Failure Files · 2/2
The content was published. The assistant had no idea.
Reindexing has to be triggered, not assumed
Alex OS only re-embeds content when the CMS calls its config-refresh route — a seed script that writes straight to the CMS's MySQL database has to call it manually.