Application structure
The application registers oneKnowledge instance and one ingest workflow with AgentOS. A small FastAPI route serves the browser UI.
Search-tuned labels
The schema separates fields that help with different queries:Reindex behavior
Reindexing performs a full rebuild. The workflow removes the existing knowledge content, then processes every URL inIMAGE_URLS with a bounded thread pool. This makes prompt and schema changes visible across the complete demo collection.
The workflow uses PostgresDb so AgentOS can persist background workflow runs. The same Postgres instance stores knowledge content, while PgVector stores embeddings and serves hybrid search.