Add commercial identity research corpus and binding concepts

Record deep research on commercial identity coupling across theory, law,
regulation, and software (KYC, LEI, DUNS, eIDAS, CRM). Introduce Commercial
Commitment, Legal Person, and Beneficial Owner to the canon model and document
the fluid-to-bound identity gradient in the conceptual model.

DownstreamRecommendations.md

@@ -107,4 +107,17 @@ later explicit package is extracted.
 | DID / VC | Identifier, Credential, Claim | Trust relationship |
 | Entity resolution | Synonymity Assertion | — |
 | Stripe / CRM billing | Commercial Record, Commercial Relationship | Subscription state |
-| Auth0 / Stytch B2B | Organization, Customer role, Tenant, Membership | Account, Subscriber label |
+| Auth0 / Stytch B2B | Organization, Customer role, Tenant, Membership | Account, Subscriber label |
+| KYC / AML / LEI / DUNS | Commercial Record, Beneficial Owner, Registry Identifier | Assurance, Evidence |
+| Salesforce / CRM | Commercial Record, Contact as Natural Person | Account hierarchy |
+
+## Commercial Binding
+
+- Model fluid identity (trials, leads, pseudonyms) without Commercial Commitment until
+  counterparty reliance exists.
+- On subscription, contract, or KYC acceptance, create Commercial Commitment with
+  Evidence Source and lifecycle state.
+- Link registry identifiers (LEI, DUNS, UEI, company reg) to Organization/Legal Entity
+  via Synonymity Assertion when multiple registries describe one entity.
+- Separate CRM Account and Stripe Customer as Commercial Records; never merge with login Account.
+- Use qualified credentials (eIDAS seal, VC) as Evidence for Commercial Commitment where applicable.