AI & Agentic Systems · Level 3 · artefact
Artefact — Retrieval corpus and query graph
Retrieval is filtered by metadata before it searches — a tagged corpus · a four-node LangGraph query graph · and a deliberate replacement of ChromaDB with Qdrant.
- Qdrant
- LangGraph
- Prefect
- n8n
- ChromaDB
Artefact — Retrieval corpus and query graph
Status: stub. The query graph diagram and an ingest run log land later; this site’s own corpus build is Phase 4.
What the artefact is
The ingest and query path: documents are chunked and tagged with metadata at ingest, stored in Qdrant, and filtered on that metadata before a similarity search runs. The LangGraph graph has four nodes; the fourth decides whether the answer can be given from what was retrieved.
What it proves
Retrieval designed around payload filtering and a hard stop, plus the reasoning for moving off ChromaDB — heavier footprint and weaker filtering — recorded as a decision rather than a migration.
When it is delivered
The query graph diagram in Phase 7. The live demonstration of the same pattern is this site’s own retrieval, delivered in Phase 4 and Phase 5.
Artefacts behind this page
- Artefact — Guardrails · hooks in the model path running
- Artefact — House AI hub service topology running
- Artefact — Memory in two layers · Engram and Headroom running
- Artefact — Model routing and cost control running
- Artefact — Paperclip and n8n pipelines in production running
- Artefact — Voice pipeline · speech in and speech out running