Blank cell
An unmatched requirement left empty in the buyer’s original spreadsheet. Blanks are the factory gap list. Orbid does not invent a specification to finish the row.
A blank cell is an honest output. When catalog evidence does not support a required value, Orbid leaves the cell empty in the original file. The list of blanks is handed to the factory as the next SKU to learn. Completing the row with a plausible number would be a form-filler or chatbot behavior, not write-back.
Why blanks are the product
Every written cell is a commitment. An invented number can void the pack. Buyers sent a locked workbook because they want their columns back, not a new narrative. Blanks keep the commitment test visible.
What blanks are not
A blank is not a software error, not “coverage below 100%,” and not a missing feature. It is the difference between a catalog you sell and a row you cannot prove. See write-back and catalog match. Device-regime examples of blanks on GPO sheets belong on the healthcare-equipment industry page.