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/eidas-eudi-legal-person-wallet.md
View file

@ -88,8 +88,12 @@ persons** carrying verifiable credentials for B2B and B2G exchange.
## Open Questions
- Should qualified electronic seal be Credential subtype tied to Legal Entity only?
- How should EUDI organizational wallet Scope relate to Tenant vs. Commercial Record?
*(none — settled in `commercial-identity-nuance-settlement.md`)*
## Settled
- Qualified seal → **Credential** `credential_type: qualified_seal` via Representation.
- Org wallet → **Scope** `wallet_scope`, linked to Commercial Record — not Tenant.
## References