Companion to the interactive entity map in data-model.html. Attributes and cardinalities are taken from the code at commit 41815d0; the source for each entity is listed below the diagram.

Only index_manifests is a relational table. The Qdrant, Redis and file entities are documents or keys, and every relationship is logical: no store enforces a foreign key, so the code keeps them consistent.

Rendering diagram…

Rules the diagram cannot show

• At most one active row. A partial unique index, one_active_index, enforces this. activate() retires the current active row and promotes a validated one inside the same connection.
• A collection is recreated if its name exists. A build that reuses an index version drops and recreates kb_{version}, and re-registering that version resets its row to building.
• Uploads share the live collection. Session uploads are chunk points written into the active collection with session_upload = true. Unscoped searches exclude them, and they have no TTL.
• Cache entries scope themselves. Namespace inputs include content_version, so a new index makes earlier entries unreachable rather than deleting them. They expire after 7 days.
• Calibration is pinned to the index. It is fitted against one content_version, and startup fails readiness when the active index differs.

Sources

Data model (ERD)