Actions

Documentation status: reference — see Maturity and evidence.

An action is a declared capability of the model. It carries business intent and an invocation signature; its concrete implementation remains behind the Runtime boundary.

Internal, published, and exposed actions

Internal: used by the model, a script, a view, or a process.
Published: marked as part of the concept's callable capabilities.
Exposed: a published action bound to a concrete access mechanism such as HTTP, an agent, messaging, or a UI.

Publication is not authorization. Authentication, authorization, visibility, and validation remain separate layers.

Canonical signature

actions:
  - action:
      name: Verify
      type: ObjectItem
      published: true
      params:
        - Login:
            dataType: String
            paramType: ptIn
        - Password:
            dataType: String
            paramType: ptIn
        - Result:
            dataType: Boolean
            paramType: ptReturn

In the polymorphic actions list, the item type is explicit: action: or actionGroup:.

Good practices

name actions with business verbs (Verify, Enroll, Finalize, Search);
stabilize the signature before exposing it;
keep long-running orchestration in a process;
do not put HTTP, UI, or RPC concerns in the business name;
do not use private implementation class names in public examples.