Structuring a logiCells Project
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
A project separates source declarations, package dependencies, assembly and publication artifacts.
Packages establish the reusable and versioned model assembly boundary. The LaTeX development guidance covers application configuration, package composition, class manifests, loading modes and conventions. A package definition is not the same as a running service or a deployment container.
Engineering rules
- Explicitly declare which packages compose an application.
- Review cross-package identity, dependencies and overrides.
- Keep naming and declaration formats aligned with the versioned grammar.
- Test package activation and ownership rather than assuming file presence implies activation.
Chapter outline (original LaTeX headings)
- Application Identity and Desktop
- Graph and Metadata Loading
- Package Items, Schema Paths, View Paths and Desktops
- Database Aliases
- Binary Packages and Model Packages
- Platform and Application Namespaces
LaTeX provenance
Primary chapter: Declarative Conceptual Programming with the logiCells Platform/developer-guide/chapters/application-configuration-and-package-assembly.tex.