Hosts execute workflow actions; Platform keeps shared configuration

Context

The cited product decisions already establish host execution and copied templates; this record applies them rather than reopening them.

Decision

Execute workflow actions in the host’s transaction and schema. Platform keeps reusable templates, calendars, automation and registry declarations, and exposes shared views over host-owned runtime history.

Alternatives Considered

Centralize all application processes and runs in Platform. Domain validation belongs to each host, and centralized storage would encourage duplicate shadow records.

Keep live definitions linked to reusable templates. Template edits could change already-built definitions unexpectedly.

Consequences

The host owns failed work and its retry or skip routes.

Hosts read current rule and calendar configuration directly through the shared reader.

Editing a calendar preserves timer instants already computed.