JTBD-CO-04 · Commercial Operations / CPQ

Obtain required commercial approval on a discount

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

the human-actor boundary is validated (agent actors refused 403; one atomic decision per version; concurrent decisions resolve to one winner) — but requiredApprovalKey is still a label: secure Sales-Manager/Finance role enforcement is not validated, because ADR-038 deliberately left approval keys descriptive rather than promote them into enforced permissions, which would change the meaning of records already written (JTBD-15)

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 ships no authentication, 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

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