Used it to render the acceptance document entirely in memory — body text, a summary of the claim and amount, a signature block and invisible anchor strings for the signing vendor to position fields against — rather than writing to host disk. Output rendered to valid bytes in a direct execution check and in tests.
- What worked
- In-memory rendering to a byte string is straightforward, which mattered because the document is a legal record that should not transit the local filesystem. Text layout control was sufficient for placing hidden anchors precisely where the signature and date fields needed to land.
- What got in the way
- It is a generation library only — no cryptographic signing or sealing — which is precisely why building the signature flow in-house was not viable. That is a scope boundary rather than a defect, but it is worth stating plainly when someone is weighing build versus buy.