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.

model/ConceptualModel.md

@@ -254,6 +254,36 @@ adjudicated tiers require Legal Entity / Organization actors.
 No standalone Reputation entity — aggregate downstream if needed; preserve tier
 provenance in canon.
 
+Optional `numeric_score` + `score_scale` on Evidence Source for downstream; tier
+enum remains canonical primary (see `commercial-identity-nuance-settlement.md`).
+
+Platform escrow with segregated funds → `Commercial Commitment` `commitment_type:
+escrow` (committed tier), not observed-only.
+
+## Standard Commercial Enums
+
+Settled nuance enums (full rationale in `commercial-identity-nuance-settlement.md`):
+
+**`control_basis`** (Beneficial Ownership Relationship): `senior_managing_official`,
+`chief_executive`, `chief_financial`, `managing_member`, `general_partner`,
+`board_chair`, `trustee`, `settlor_with_control`, `other_control` (+ detail text).
+
+**`binding_trigger`** (Pipeline Pursuit → Commercial Commitment): `quote_accepted`,
+`loi_signed`, `purchase_order_executed`, `contract_executed`, `subscription_activated`,
+`regulatory_onboarding_complete`, `org_policy_closed_won` (requires policy Evidence).
+
+**`commitment_type`** (Commercial Commitment): `contract`, `subscription`,
+`payment_mandate`, `purchase_order`, `escrow`, `regulatory_onboarding`, `amendment`.
+
+**`authority_class`** (Registry Identifier): `government_registry`, `regulatory_global`,
+`commercial_proxy`, `tax`, `industry_association`.
+
+**Cross-registry Synonymity default strength:** LEI↔company reg/ALEI/UEI strong;
+LEI↔DUNS medium; DUNS↔company reg medium.
+
+**Reputation portability:** Synonymity `linked_to`, weak default, between Reputation
+Signals across scopes.
+
 ## Scenario Gaps
 
 No scenario requires glossary or principle changes that the current model