# EM-PRD-02 provider comparison

Claude and Grok agree to complete reserved WM-ACT-004 as a narrowed Service Definition and allocate no new model or runtime identifier. The definition owns durable identity, immutable outcome semantics, eligible consumer scope and accountable-provider role type. Product, offering, process, software component, API, endpoint, subscription, request, fulfilment, SLA and observation remain externally mastered.

Both preserve Service identity when provider, implementation, endpoint, channel, price or process changes while the expected outcome, consumer scope and accountability remain stable. Multiple operational providers and realizations therefore use effective-dated bindings. The provider role type belongs to the definition; incumbent parties and mechanisms belong to external masters and bindings.

Both place catalogue presentation, eligibility presentation, commercial terms and optional price in the shared EM-PRD-01 Offering Catalogue candidate. One definition may have many offerings and one offering may compose several definitions. Grok sharpened that catalogue membership is not an identity invariant: a non-requestable internal Service may exist without an offering, but a requestable or subscribed Service must resolve an external offering row. Withdrawal of that row never retires or mints the Service.

Grok rejected independent identity for Service Consumption in this contour. Consumption is derived from entitlement, request and fulfilment records keyed by Service, offering and party. It also rejected a public business identifier for Service Dependency. A dependency is a persistable owned association with source, target, type, scope and effective interval; internal persistence keys do not create a new enterprise root. A dependency targets a Service definition or already-identified capability, never a process, component or endpoint.

SLA/SLO commitments, thresholds, measurements and breach decisions remain external. Those authorities must accept a Service-definition join key. Missing join capability is a publication hold, not permission to copy their data into WM-ACT-004.

The reconciled candidate records 38 constraints and 28 fixtures. It remains a held completion candidate because the Offering Catalogue is unallocated, role/party and realization references need confirmed masters, dependency taxonomy is not canonical, join-key and collision checks remain, and live publication verification has not occurred.