Pack gate
The intake check that accepts a goods specification pack and refuses service proposals and works or install packs. Same compiler; wrong file type does not enter write-back.
The pack gate is the first step of Orbid. The desk brings the spreadsheet the buyer sent. If the pack is a goods specification workbook — locked cells, required rows, catalog-shaped columns — it proceeds to catalog match and write-back. If the pack is a service proposal, a construction scope, or an install bundle, Orbid refuses it. The product does not write prose bids.
Why a gate exists
A goods cell is a SKU commitment. A service line is a different job. Mixing them on one compiler would invent answers the factory cannot ship. The gate keeps the original-file promise honest.
What happens after the gate
Accepted packs go to catalog match. Each required row is bound to a product you sell, or marked as a gap. Proven cells write back. Unproven cells stay blank. Healthcare equipment packs (GPO, hospital, VA) use the same gate; they are an industry slot, not a different product.