From 4e977737ee3671c453af369ab65863285bb7110d Mon Sep 17 00:00:00 2001
From: Mikhail Chusavitin <mchusavitin@mchusmbp.local>
Date: Sat, 7 Mar 2026 21:13:08 +0300
Subject: [PATCH] Document legacy BOM tables

---
 bible-local/03-database.md    | 11 +++++++++++
 bible-local/09-vendor-spec.md |  8 ++++++++
 2 files changed, 19 insertions(+)

diff --git a/bible-local/03-database.md b/bible-local/03-database.md
index d020899..e4dfb9a 100644
--- a/bible-local/03-database.md
+++ b/bible-local/03-database.md
@@ -113,6 +113,17 @@ Database: `RFQ_LOG`
 | `qt_partnumber_book_items` | PN→LOT mapping rows (written by PriceForge) | SELECT |
 | `qt_vendor_partnumber_seen` | Vendor PN tracking for unresolved/ignored BOM rows (`is_ignored`) | INSERT only for new `partnumber`; existing rows must not be modified |
 
+Legacy server tables not used by QuoteForge runtime anymore:
+
+- `qt_bom`
+- `qt_lot_bundles`
+- `qt_lot_bundle_items`
+
+QuoteForge canonical BOM storage is:
+
+- `qt_configurations.vendor_spec`
+- row-level PN -> multiple LOT decomposition in `vendor_spec[].lot_mappings[]`
+
 `qt_client_schema_state` current contract:
 
 - identity key: `username + hostname`
diff --git a/bible-local/09-vendor-spec.md b/bible-local/09-vendor-spec.md
index b1853ba..a34b95f 100644
--- a/bible-local/09-vendor-spec.md
+++ b/bible-local/09-vendor-spec.md
@@ -18,6 +18,14 @@ The vendor spec feature allows importing a vendor BOM (Bill of Materials) into a
 `vendor_spec` is a JSON array of `VendorSpecItem` objects stored inside the configuration row.
 It syncs to MariaDB `qt_configurations.vendor_spec` via the existing pending_changes mechanism.
 
+Legacy storage note:
+
+- QuoteForge does not use `qt_bom`
+- QuoteForge does not use `qt_lot_bundles`
+- QuoteForge does not use `qt_lot_bundle_items`
+
+The only canonical persisted BOM contract for QuoteForge is `qt_configurations.vendor_spec`.
+
 ### `vendor_spec` JSON Schema
 
 ```json