Define role and actions of Service Provider Persona in OpenControlPlane

[maximiliantech]

Goal

Define the operational role of a Service Provider in the OpenControlPlane ecosystem. Today the Platform Owner controls which service versions are available to end users. This epic closes the gap by producing an ADR and team-agreed proposal for how a Service Provider publishes, versions, and manages its offerings.

Planned for Q4/2026.

Context

The getting started documentation describes three personas (End User, Platform Owner, Service Provider) and covers how to create technical artifacts (service-provider-* repositories, controllers). What is missing is guidance on the operational side: once a Service Provider has built something, how does it actually act as a service provider? How are new versions released, made available, and eventually deprecated?

Tasks

• Write ADR in openmcp-project/docs covering the Service Provider release and offering lifecycle
• Define how a Service Provider publishes a new service version into the ecosystem
• Define how a Service Provider makes a version available to end users (and the relationship to Platform Owner responsibilities)
• Define deprecation and removal flow for a service version
• Team review and consensus on the proposal

Acceptance Criteria

• ADR merged into openmcp-project/docs
• Team has reviewed and agreed on the proposal
• Guidance is clear enough for an external Service Provider developer to follow

Milestone

Q4/2026: ADR accepted by team

Dependencies

• tbd

Stakeholders

Service Provider developers, Platform Owners, OpenControlPlane core team