Resolve payment credential and CRM pipeline commitment boundaries

Add research on PCI/tokenized payment references vs login Credentials (Payment
Instrument Reference, Payment Mandate) and CRM Opportunity promotion thresholds
(Pipeline Pursuit, binding_trigger). Resolve OpenQuestions for both topics.
Update glossary, conceptual model, terminology, and downstream recommendations.
This commit is contained in:
2026-06-21 23:11:00 +02:00
parent bd272151af
commit 6ea582cd9e
11 changed files with 435 additions and 19 deletions

View File

@@ -73,14 +73,20 @@ a company or household you sell to, distinct from **Contact** (people) and **Use
| Account-Contact Relationship | Affiliation / Representation |
| Account hierarchy | Organization structure Relationship |
| Lead | Prospective Commercial Record (weak) |
| Opportunity | Commercial Commitment (pipeline stage) |
| Opportunity | Pipeline Pursuit (promotes to Commercial Commitment on binding trigger) |
| User | Account (internal operator) |
| Person Account | Commercial Record + Natural Person (combined projection) |
## Open Questions
- Should pipeline Opportunity map to Commercial Commitment subtype or downstream only?
- How should Person Account be discouraged in canon-aligned adapters?
- Renewal Opportunity — Pipeline Pursuit vs. commitment amendment.
## Resolved (see crm-pipeline-commitment-threshold.md)
- Opportunity → **Pipeline Pursuit**; Commercial Commitment only on binding trigger
(signed LOI/quote, executed PO/contract, active subscription). Forecast "Commit"
category is not Commercial Commitment.
## References