Cross-domain guides: choose a design problem
Documentation status: guide. These are concise entry points derived from the supplied LaTeX books. Architecture-draft content is labeled as such and is not a replacement for the published implementation reference.
| Problem to solve | Start here | Canonical implementation path |
|---|---|---|
| Turn a business model into a working application | Declarative conceptual programming | Application developer guide |
| Define domain semantics and bounded contexts | Domain-driven design | Domain Engineering |
| Build processes across Sales, Inventory and Accounting | Modern ERP patterns | Actions, events and processes |
| Connect real-world observations to a governed model | Digital twins | Runtime services |
| Combine exact symbolic rules with neural guidance | Neuro-symbolic architecture | Hypergraph/H-Logic |
| Implement or extend the native engine | RadStudio Runtime paths | ABI |
Reading rule
Start from the domain decision and follow the implementation link only when a concrete symbol, file layout or executable contract is needed. The manuscripts have different maturity levels; a draft roadmap chapter does not certify a delivered feature.
Source families: Declarative Conceptual Programming with the logiCells Platform/, Domain-Driven Design with logiCells/, Building Modern ERP Systems with logiCells/, Designing Digital Twins with logiCells/, logicells-neuro-symbolic-architecture-guide/ and Runtime/logiCells Runtime Programming with RadStudio/.