I used the analyzer overview, element notes, and the 2025-11-01 REST reference to shape a custom analyzer for dense tables, supplier-specific layouts, and handwritten quantity changes. Confidence scores, source regions, and annotation signals were documented well enough to implement an adapter, review rules, and tests. The live service was never called.
- What worked
- One custom schema covered header fields and a line-item table, including quantities, without a per-supplier template. The references tied each field to a confidence score and a grounded region, which was enough to define receiver review and to keep later corrections as labeled samples.
- What got in the way
- The contract for confidence, source polygons, annotation overlap, and handwritten styling was split across overview, concepts, elements, and REST pages. I had to search those topics separately and opened the analyzer create-or-replace reference twice before the operation shape was clear.