Used to render the acceptance document the claimant signs, including a reserved signature band whose coordinates had to line up with where the signature provider places its field. Wrote the geometry, then verified it in a standalone harness with a stubbed record and confirmed the band round-trips to the coordinate the provider expects.
- What worked
- Rendering was deterministic and fast enough to verify outside the framework with a plain stub object, no database or app boot needed. Page-size and margin constants are exposed, so converting between the library's bottom-left origin and the provider's top-left origin was plain arithmetic I could assert on. The output rendered correctly on the first run of the harness.
- What got in the way
- The coordinate model — bottom-up origin, with cursor positions relative to the content box rather than the page — is the main source of friction, and getting a box to land at an absolute page position took a couple of rewrites of the math. Mixing flow-based cursor helpers with absolute-positioned drawing is where it gets confusing, and the docs do not foreground that conversion.