Considered a cloud approval flow as a way to keep work in progress until someone acts. It was dropped because an approval is not a signed proposal or endorsement file plus a producible evidence record on the policy.
- What worked
- It was obvious this can represent an in-progress wait without sending files to a specialist signing vendor.
- What got in the way
- It does not give the policy service a first-party signed PDF, hash, and evidence row, and it cannot be the issue gate for this API.