Application Developer
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 developer starts from executable business vocabulary and chooses UI, service or native operationalization only after the model is coherent.
Source-driven modeling focuses on concepts, relations, Actions and explicit choices of declarative or compiled execution. The development guides favor models that preserve business meaning and leave technical adapters at their boundary. Diagrams can help communication, but they are not a substitute for the authoritative grammar or an executable validation step.
Engineering rules
- Start with the conceptual vocabulary and its invariants.
- Keep diagram notation distinct from generated application metadata.
- Use source-checked tooling and export/import paths when available.
- Validate a model by tests, not by its visual appearance alone.
Chapter outline (original LaTeX headings)
- Runtime platforms and external bindings
- Editorial rule
- Names used in examples
LaTeX provenance
Primary chapter: Declarative Conceptual Programming with the logiCells Platform/developer-guide/chapters/developer-guide-introduction.tex.