One structured record — readable by software, checkable by people, traceable to source.
The truth about a product lives across PDF datasheets, IES and LDT photometric files, installation documents, test reports, and compliance records — each formatted its own way, each written to be read one at a time.
Every design tool and AI agent that needs those values must re-extract them from documents made for the eye. What reaches the tools is an extraction layer's guess, not the manufacturer's source.
That worked while designers read one datasheet at a time. It breaks when an AI must read a hundred to answer a single question.
ULC turns the documents manufacturers already publish into one structured .ulc record that design tools and AI read without an extraction step.
The datasheet stays beautiful for human reading. The record stays exact for machine reading.
Not one orderable SKU, and not automatically one IES file — one measured or declared scenario, connected to the configurations it covers and the evidence behind every value.
One scenario can cover thousands of SKUs.
Both views are generated by the reference builder and checked for parity. Neither can be typed in by the author.
Every grade names its gaps — the validator prints the exact roadmap from Incomplete to Full.
ULC records the evidence; it does not certify the product.
Documented means a qualifying attestation has current evidence attached and hash-anchored.
FREE VALIDATOR DOWNLOAD FOR MANUFACTURERS · OFFLINE · DETERMINISTIC · MACOS / WINDOWS / LINUX
Manufacturers emit ULC from the systems they already use. Both routes end in the same open schema, generated index, and validator.
ULC does not replace the PDF, IES, LDT, PIM, rep, distributor, or software platform. It gives them a common source of structured luminaire data.
One structured record — readable by software, checkable by people, traceable to source.