LATTICE DDC Integration, Qdrant, and BOQ

To assign ERP item identifiers to IFC elements, you run a BOQ ingest pass that populates rows with erp_item_id, unit_cost, and quantity, then rolls up the results into lattice/execution/boq_items for downstream reporting.

Semantic search for DDC skills works by querying the Qdrant ddc-skills collection by similarity, which requires strict count parity between meta/DDC_MAPPING.md and the collection to ensure no stale or missing mappings exist.

The best way to verify BOQ cost coverage is to run CI-oriented scoring and audit scripts that detect null erp_item_id values after ingest and validate that all IFC elements are fully populated.

Yes, BOQ ingest requires single-writer locking to prevent concurrent data conflicts, ensuring ERP item identifiers and cost rollups are accurately assigned to IFC elements without race conditions.

Stale or incomplete DDC skill mapping results occur when count parity fails between meta/DDC_MAPPING.md and the Qdrant collection, requiring a re-index of the DDC skills to synchronize the data.

Yes, you need to perform Qdrant health checks before running semantic lookup to verify the collection is operational and ensure DDC skill queries return accurate, synchronized results.