Application
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
The Application boundary groups activated capabilities over assembled conceptual metadata; it is not just an executable file.
A logiCells application is assembled from executable conceptual declarations, not just a set of screens or database tables. Source chapters distinguish application configuration, packages, classes, actions and the runtime objects they produce. Model assembly is a deliberate step between authoring declarations and invoking behavior.
Engineering rules
- Define the application boundary and package dependencies first.
- Use conceptual Actions for business intentions, not interface-specific command names.
- Distinguish metadata assembly from the execution of objects and contexts.
- Validate declarations and generated contracts before publishing services or views.
Chapter outline (original LaTeX headings)
- From Application as Program to Application as Model
- What Makes a Model Executable
- The Application Boundary
- Actions as Part of the Model
- Views as Optional Projections
- Why Executability Matters
LaTeX provenance
Primary chapter: Declarative Conceptual Programming with the logiCells Platform/developer-guide/chapters/applications-as-executable-conceptual-models.tex.