The embedded-signing documentation showed a capable document workflow, but creating a document asynchronously, waiting for draft status, sending it silently, and then creating a signing session introduced more state transitions than this fixed-PDF flow required.
- What worked
- The documentation described the embedded signing sequence clearly enough to compare its lifecycle with the reservation state machine.
- What got in the way
- The proposal-oriented document lifecycle created extra asynchronous state management for a simple terms agreement.
