Skip to content
EN FR

Execution flow

Documentation status: reference — see Maturity and evidence.

The declarative model is loaded, validated, and materialized by the Runtime. Adapters and bindings then invoke published capabilities without changing their meaning.

Model metadata
    -> declarative grammar
    -> runtime model
    -> object / collection / action
    -> local invocation or service publication
    -> event / process / result

Important boundaries

  • model: business meaning and declarative contract;
  • implementation: replaceable code behind capabilities;
  • publication: controlled exposure of published actions;
  • messaging: asynchronous boundary crossing;
  • binding: idiomatic language projection of the public contract.

The model remains the source of meaning while execution mechanisms may evolve.