coulomb/commerce-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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:
tegwick 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

8
research/commercial-identity/kyc-aml-commercial-identity-binding.md
View file

@ -90,12 +90,12 @@ high-stakes counterparty records**.
## Open Questions
- Standard `control_basis` enum across US CDD and EU AMLD wording.
- How to model BOI registry volatility in lifecycle without canon becoming legal advice?
*(none — settled in `commercial-identity-nuance-settlement.md`)*
## Resolved (see beneficial-ownership-kyc-boi.md)
## Settled
- Beneficial Owner → **Beneficial Ownership Relationship** (dedicated type, not Ownership subtype).
- Beneficial Owner → **Beneficial Ownership Relationship**; `control_basis` enum;
CDD vs. BOI filing layered separately.
## References