Settle commercial identity nuances with consolidated enums and linking rules

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:
2026-06-21 23:21:21 +02:00
parent 6ea582cd9e
commit 08361f6fb7
18 changed files with 403 additions and 64 deletions

View File

@@ -135,4 +135,12 @@ later explicit package is extracted.
- Never store PAN/CVV in identity-layer stores; use Payment Instrument Reference only.
- Map SetupIntent/mandate success to Payment Mandate Commercial Commitment.
- Map CRM Opportunity to Pipeline Pursuit; promote to Commercial Commitment only on binding_trigger.
- Do not treat Salesforce Forecast "Commit" as Commercial Commitment active state.
- Do not treat Salesforce Forecast "Commit" as Commercial Commitment active state.
- Use settled enums from `commercial-identity-nuance-settlement.md`: `control_basis`,
`binding_trigger`, `commitment_type`, cross-registry Synonymity strengths.
- Person Account adapters: split Natural Person + Commercial Record; export combined
projection only with `projection_mode: person_account_combined`.
- FinCEN ID → Registry Identifier on Natural Person; BO exemptions → explicit Evidence.
- LEI↔DUNS Synonymity default medium; LEI↔company reg default strong.
- Reputation portability: `linked_to` Synonymity weak between Reputation Signals.
- Oracle/escrow release → Performance Evidence; ADR/court → Adjudication Outcome.