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.

research/commercial-identity/commercial-identity-synthesis.md

@@ -121,13 +121,13 @@ Model as lifecycle events, not silent merges:
 
 ## Research Gaps
 
-- Standard `binding_trigger` enum across CRM adapters.
-- Network token (Visa VTS) mapping to Payment Instrument Reference.
-- Smart contracts and automated Commercial Commitment lifecycle.
-- Synonymity strength bands for LEI ↔ DUNS ↔ company reg crosswalks.
-- Cross-platform reputation portability (Synonymity between Reputation Signals).
-- Smart-contract / oracle outcomes — observed vs. adjudicated tier placement.
-- Standard `control_basis` enum for Beneficial Ownership across jurisdictions.
+- Smart contracts and automated Commercial Commitment lifecycle (implementation patterns).
+- National statute variants beyond settled enum baselines (downstream legal config).
+
+## Nuance settlement
+
+Commercial identity edge-case enums and linking rules are consolidated in
+`commercial-identity-nuance-settlement.md` (2026).
 
 ## Source Notes in This Stack
 
@@ -143,6 +143,7 @@ Model as lifecycle events, not silent merges:
 - `reputation-assurance-gradient.md`
 - `payment-credential-pci-boundary.md`
 - `crm-pipeline-commitment-threshold.md`
+- `commercial-identity-nuance-settlement.md`
 - `../commercial-subscription/b2b-saas-subscriber-tenancy.md`
 - `../commercial-subscription/stripe-customer-billing.md`