EM-COM-01 · Enterprise profiles · Published 0.1.0

Enterprise Counterparty Relationship

Represent customer, supplier and partner roles for one Party without duplicating Party identity, upstream relationship records or contact endpoint values.

4 bundles · 8 layers · 16 findings · 32 questions

Required adoption limits

Use only with authoritative Party resolution, pinned upstream records and the semantic evaluator. The profile does not own Party identity, relationship lifecycle, endpoint values, consent or classification schemes.

Publication addendum and exact limits

Use in a Company Dimension

Anchor one profile set to an authoritative Party and observing Dimension; bind existing customer/supplier/partner records; assign existing contact endpoints by purpose and time; retain sourced segmentation assertions.

Research assurance: reviewable-draft. This is a bounded original companion. No Party matching, endpoint ownership, consent decision, contract/order lifecycle or group-membership authority is supplied. Adoption limits.

Bundles → Layers → Findings → Questions

Collect the expected evidence for each question. Unknown context remains explicit. Listed actions confer no operational permission.

CPR-B1Identity and authority2 layers

Govern identity and authority without duplicating upstream identity or authority.

CPR-L1Party anchoring2 findings

Make party anchoring explicit and testable.

CPR-F1

Set identity

Validate set identity against the bounded profile contract.

Questions
  1. CPR-Q1 Which Party and observing Dimension identify this set?evidence
    Expected answer
    • Set identity
  2. CPR-Q2 Can any role create another Party?decision
    Expected answer
    • Set identity
Artifacts
  • Set identity evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-F2

Party master

Validate party master against the bounded profile contract.

Questions
  1. CPR-Q3 Which authority resolves partyRef?evidence
    Expected answer
    • Party master
  2. CPR-Q4 Is a split Party master held rather than hidden?decision
    Expected answer
    • Party master
Artifacts
  • Party master evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-L2Commercial authorities2 findings

Make commercial authorities explicit and testable.

CPR-F3

Role ownership

Validate role ownership against the bounded profile contract.

Questions
  1. CPR-Q5 Which upstream model owns this role?evidence
    Expected answer
    • Role ownership
  2. CPR-Q6 Does customer resolve only to 014 and supplier/partner to 015?decision
    Expected answer
    • Role ownership
Artifacts
  • Role ownership evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-F4

Exact referent

Validate exact referent against the bounded profile contract.

Questions
  1. CPR-Q7 Which versioned upstream record is bound?evidence
    Expected answer
    • Exact referent
  2. CPR-Q8 Is lifecycle copied into the profile?decision
    Expected answer
    • Exact referent
Artifacts
  • Exact referent evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-B2Scope and roles2 layers

Govern scope and roles without duplicating upstream identity or authority.

CPR-L3Concurrent roles2 findings

Make concurrent roles explicit and testable.

CPR-F5

Multi-role set

Validate multi-role set against the bounded profile contract.

Questions
  1. CPR-Q9 Which roles are active at the requested time?evidence
    Expected answer
    • Multi-role set
  2. CPR-Q10 Does adding a role preserve Party identity?decision
    Expected answer
    • Multi-role set
Artifacts
  • Multi-role set evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-F6

Role validity

Validate role validity against the bounded profile contract.

Questions
  1. CPR-Q11 What half-open interval applies to each binding?evidence
    Expected answer
    • Role validity
  2. CPR-Q12 How is upstream supersession surfaced?decision
    Expected answer
    • Role validity
Artifacts
  • Role validity evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-L4Account scope2 findings

Make account scope explicit and testable.

CPR-F7

Scope kind

Validate scope kind against the bounded profile contract.

Questions
  1. CPR-Q13 Is the frame seller, buyer, legal entity or group?evidence
    Expected answer
    • Scope kind
  2. CPR-Q14 Which target resolves the scope?decision
    Expected answer
    • Scope kind
Artifacts
  • Scope kind evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-F8

Group boundary

Validate group boundary against the bounded profile contract.

Questions
  1. CPR-Q15 Which group perimeter authority is referenced?evidence
    Expected answer
    • Group boundary
  2. CPR-Q16 Is membership inferred from tax ID or CRM hierarchy?decision
    Expected answer
    • Group boundary
Artifacts
  • Group boundary evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-B3Contacts and classification2 layers

Govern contacts and classification without duplicating upstream identity or authority.

CPR-L5Contact assignment2 findings

Make contact assignment explicit and testable.

CPR-F9

Endpoint reference

Validate endpoint reference against the bounded profile contract.

Questions
  1. CPR-Q17 Which WM-PER-010 endpoint is assigned?evidence
    Expected answer
    • Endpoint reference
  2. CPR-Q18 Does the assignment copy an endpoint value?decision
    Expected answer
    • Endpoint reference
Artifacts
  • Endpoint reference evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-F10

Assignment context

Validate assignment context against the bounded profile contract.

Questions
  1. CPR-Q19 Which purpose, role, scope and interval apply?evidence
    Expected answer
    • Assignment context
  2. CPR-Q20 Does assignment imply consent or reachability?decision
    Expected answer
    • Assignment context
Artifacts
  • Assignment context evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-L6Segmentation assertions2 findings

Make segmentation assertions explicit and testable.

CPR-F11

Sourced segment

Validate sourced segment against the bounded profile contract.

Questions
  1. CPR-Q21 Which code, scheme, version and source support this assertion?evidence
    Expected answer
    • Sourced segment
  2. CPR-Q22 Is a bare segment label rejected?decision
    Expected answer
    • Sourced segment
Artifacts
  • Sourced segment evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-F12

Assertion history

Validate assertion history against the bounded profile contract.

Questions
  1. CPR-Q23 Which method and asserted time apply?evidence
    Expected answer
    • Assertion history
  2. CPR-Q24 Are conflicts retained and corrections appended?decision
    Expected answer
    • Assertion history
Artifacts
  • Assertion history evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-B4Projection and controls2 layers

Govern projection and controls without duplicating upstream identity or authority.

CPR-L7Current projections2 findings

Make current projections explicit and testable.

CPR-F13

rolesAt

Validate rolesat against the bounded profile contract.

Questions
  1. CPR-Q25 Which bindings are active at time t?evidence
    Expected answer
    • rolesAt
  2. CPR-Q26 Does projection mint a relationship?decision
    Expected answer
    • rolesAt
Artifacts
  • rolesAt evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-F14

contactsFor

Validate contactsfor against the bounded profile contract.

Questions
  1. CPR-Q27 Which assignments match purpose and time?evidence
    Expected answer
    • contactsFor
  2. CPR-Q28 Is current permission rechecked at endpoint authority?decision
    Expected answer
    • contactsFor
Artifacts
  • contactsFor evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-L8Boundary controls2 findings

Make boundary controls explicit and testable.

CPR-F15

Endpoint conflict

Validate endpoint conflict against the bounded profile contract.

Questions
  1. CPR-Q29 Is the PER-010/XCT-024 conflict still visible?evidence
    Expected answer
    • Endpoint conflict
  2. CPR-Q30 Can XCT-024 become a second party endpoint master?decision
    Expected answer
    • Endpoint conflict
Artifacts
  • Endpoint conflict evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.
CPR-F16

Neighbor exclusion

Validate neighbor exclusion against the bounded profile contract.

Questions
  1. CPR-Q31 Which contract, order, consent and event refs remain external?evidence
    Expected answer
    • Neighbor exclusion
  2. CPR-Q32 Does any profile field absorb their lifecycle?decision
    Expected answer
    • Neighbor exclusion
Artifacts
  • Neighbor exclusion evidenceReference or assertion needed to answer this finding.
Actions and unknown handling
  • Run the profile validation without changing an upstream master.

Research and validation

Claude's frozen R3 audit accepted the implementation with limits after display-cache and documentation fixes. Grok independently supported the profile boundary and Party-by-observer identity; it did not execute or frozen-audit the final code. Executed tests and native checks are recorded separately. Research dossier · Review and limits · Tests · Native acceptance · Checksums.

Catalogue identity: vr.profile.enterprise-counterparty-relationship. EM-COM-01 remains a broader, partially covered research contour. Parent models are semantic references; no subtype or whole-parent conformance is asserted.