coulomb/identity-canon
Archived
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Settle commercial identity nuances with consolidated enums and linking rules

Browse Source 
Add commercial-identity-nuance-settlement.md resolving control_basis,
binding_trigger, cross-registry Synonymity strengths, OPI branch modeling,
escrow commitment type, reputation portability, payment edge cases, CRM renewal
rules, Person Account adapters, and eIDAS wallet scope. Update canon, OpenQuestions,
and all commercial-identity source notes.
This commit is contained in:
Bernd Worsch
2026-06-21 23:21:21 +02:00
parent 6ea582cd9e
commit 08361f6fb7
18 changed files with 403 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
research/commercial-identity/salesforce-crm-commercial-record.md
View File

@@ -79,14 +79,13 @@ a company or household you sell to, distinct from **Contact** (people) and **Use
## Open Questions
- How should Person Account be discouraged in canon-aligned adapters?
- Renewal Opportunity — Pipeline Pursuit vs. commitment amendment.
*(none — settled in `commercial-identity-nuance-settlement.md`)*
## Resolved (see crm-pipeline-commitment-threshold.md)
## Settled
- Opportunity → **Pipeline Pursuit**; Commercial Commitment only on binding trigger
(signed LOI/quote, executed PO/contract, active subscription). Forecast "Commit"
category is not Commercial Commitment.
- Opportunity → **Pipeline Pursuit**; binding triggers and renewal/amendment rules.
- Person Account → split Natural Person + Commercial Record; adapter `projection_mode`
only on export.
## References