JTBD-CO-05 · Commercial Operations / CPQ

Create a signature envelope with a provider

partially supported. Part of the job works and is proved; the rest is named rather than implied. Read what is excluded before planning around it.

What the catalogue records

validated only for the deterministic fixture signature provider: human-actor send boundary (agents refused 403), exactly one envelope per quote version with a deterministic idempotency key, the provider call outside every transaction, a monotonic envelope/signer state machine, and a recoverable failed state with explicit reconciliation. No real DocuSign / Adobe Sign / Dropbox Sign integration exists or is claimed, and no credential ships

Evidence

This row carries no test path of its own in the structured index. The matrix records the evidence for it in a block shared with neighbouring rows, which jobs.json does not split per row — so read docs/benchmarks/CRM_JTBD_MATRIX.md for it. The status above was set from that evidence, not from its absence.

What this status does not mean

A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework is local-development-only: there is no authentication, tenancy or RBAC, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.

Other jobs in Commercial Operations / CPQ

Create a Quote from a Price Book — validated end to end
Synchronize an external catalog (Stripe/Zuora/ERP/custom) — partially supported
Request a discount under a deterministic policy — validated end to end
Obtain required commercial approval on a discount — partially supported
Verify signing via verified provider events — partially supported
Create an immutable signed Order snapshot — validated end to end

All 7 jobs in Commercial Operations / CPQ · the whole catalogue