Actions, events and processes
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
An Action states intent, an Event reports a domain occurrence, and a Process coordinates steps over time.
Actions express intent, Events record meaningful change, and Processes coordinate longer business work. They are complementary modeling concepts, not aliases for HTTP verbs or UI callbacks. The source stresses clear ownership of decisions and preservation of context across execution and publication.
Engineering rules
- Name Actions after business intentions and enforce their preconditions.
- Emit Events for actual domain occurrences, not assumed transport deliveries.
- Represent cross-step coordination as an explicit Process where needed.
- Test authorization and result invariants across every execution surface.
Chapter outline (original LaTeX headings)
- Why Actions Belong to Concepts
- Object-Level and Class-Level Actions
- Scripted and Native Implementations
- Parameters as Conceptual Boundaries
- Published Actions
- Actions in Processes
LaTeX provenance
Primary chapter: Declarative Conceptual Programming with the logiCells Platform/developer-guide/chapters/actions-as-business-intentions.tex.