EM-COM-01 · Subject model · W1
Relationships with customers, suppliers and partners
Counterparty roles, relationships, contact assignments and segmentation. The person or organization itself is reused by identity.
Result published
Claude: complete-study-and-frozen-release-audits; Grok: complete-study-and-frozen-release-audits.
Published results
Research note, in Russian: The 0.1.0 release is immutable and accepted for its bounded profile. Future semantics require a new version.
Subject boundary and candidate types
- PartyRelationship
- CustomerAccount
- SupplierRelationship
- PartnerRelationship
- ContactAssignment
Deep research questions
- How does one organization become both a customer and a supplier?
- What does a customer account mean for a group of legal entities?
- Where is the boundary between B2B and B2C profiles?
Verifiable invariants
- A counterparty role does not create a new Party
- A contact has a term and a context
- A segment is a classification with a source
End-to-end acceptance scenario
One Party with three commercial roles, different contacts and two contracts does not produce three identities.
Negative case
An organization is duplicated after the first purchase from an existing customer.
Approaches to compare
- TM Forum SID: party/customer/product/service
- OASIS UBL: trade documents and exchange
- CRM/CPQ/order management practice: stages and source boundaries
Candidates in the live catalogue
- WM-ORG-014 · Customer / Account Relationship · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ORG-015 · Supplier / Partner Relationship · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-PER-010 · Contact Point / Party Profile · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-XCT-024 · Contact Point · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.