Skip to content
EN FR

Service publication

Documentation status: reference — see Maturity and evidence.

A published service is a controlled projection of a model capability. The business contract should be defined before choosing the transport.

Publication chain

concept
  -> published action / collection
  -> service adapter
  -> route or protocol
  -> machine-readable contract

Principles

  • publish explicit capabilities rather than implementation details;
  • separate business contract, transport, and security;
  • make errors and authorization rules explicit;
  • distinguish short calls, asynchronous operations, and durable jobs;
  • document operational differences between local and remote execution;
  • version incompatible changes.

API and OpenAPI

When the transport is HTTP, an OpenAPI contract can document exposed routes, schemas, and responses. OpenAPI describes the HTTP interface; it does not replace the conceptual model or Runtime contract.