Service Publication

Documentation status: architecture — see Maturity and evidence.

Service publication exposes model capabilities to external or remote consumers.

Separation of responsibilities

model capability
    -> published action / collection
    -> service adapter
    -> protocol or route
    -> client contract

The protocol does not define the business domain. The same capability may be exposed through HTTP, RPC, messaging, or another transport where supported by the Runtime and product.

Rules

• publish only required capabilities;
• version client-visible contracts;
• enforce authorization on the capability, not only on the route;
• distinguish short calls, asynchronous processing, and durable jobs;
• make retries, idempotency, timeout, and cancellation explicit;
• document differences between local and remote execution.