Why Commercial GL came first
Commercial GL appears across procurement, certificates, broker submissions, policy packages, and compliance workflows. It is a natural first wedge because it touches many buyers and many downstream systems.
The fields are also representative: named insured, policy number, dates, occurrence limits, aggregate limits, additional insured posture, waiver posture, and evidence references.
The proof gate teaches the engine
Commercial GL hardening created the early FastScript pattern: classify the document, find candidate facts, attach evidence, normalize fields, preserve unresolved values, and benchmark against real public documents.
That pattern became reusable. Each new schema still needs its own corpus and rules, but the control discipline carries forward.
The lesson
The lesson from Commercial GL is that a schema should not be promoted because it looks good in one demo. It should be promoted when it survives repeatable scoring.
That is the difference between product and theater. The public page can say what passed, what is still hardening, and why the boundary exists.