Seeking builder feedback: reusable Daml package for structured settlement workflows on Canton

Hi Canton builders,

We’re working on a reusable Daml package for structured settlement workflows on Canton, starting with a 3-party DvP wedge.

The problem we’re trying to solve is simple: teams keep rebuilding the same workflow plumbing for each new settlement use case — proposal, acceptance, disclosed contract handling, expiry/cancel paths, and settlement completion.

Our current framing is not a general execution layer or a new app. It’s a reusable workflow primitive underneath structured Canton applications.

We’d value feedback on a few specific questions:

1. Do you see a real need for a reusable settlement workflow layer on Canton?
2. For structured settlement flows, what parts of the workflow are most painful to rebuild today?
3. Would you expect teams to adopt a reusable Daml package for this, or do they prefer app-specific logic?
4. What would make this useful enough to integrate instead of rebuilding in-house?
5. For a first wedge, does 3-party DvP feel like the right starting point?

If you’ve built on Canton or are planning to, we’d appreciate candid feedback — especially from teams working on settlement, lending, RFQ, treasury, or other multi-party workflows.

Thanks.