logiCells Developer Documentation

Documentation status: guide — see Maturity and evidence.

The model does not remain documentation. It executes. logiCells is a Runtime placed under existing applications, services and tools; the same published conceptual contract can be projected through generated bindings and local or remote execution.

logiCells.net is the detailed technical reference for the logiCells framework. It is intended for developers, architects, and integrators who have already discovered logiCells and now want to build, integrate, deploy, or understand the framework in depth.

If you are discovering logiCells for the first time, start with logiCells.com. The .com site owns discovery, positioning and product-level orientation; logiCells.net owns developer depth, technical contracts, implementation guides and reference material.

Direct access — no menu drilling

I want to…	One-click destination
Find a page by what I need to do	Browse by task
Start an application	First verified run
Build a declarative model	Declarative application guide
Write H-Logic or functionalP	H-Logic reference / functionalP
Program or extend the native Runtime	Native Runtime paths
Integrate and deploy services	Runtime operations
Read by role or by business scenario	Roles / Guides
Find any document	Full A–Z index

Start with a running Runtime

New developers should begin with Getting Started: prerequisites, platform matrix, first verified run, and project conventions. Do not start by copying model files into an environment whose Runtime boundary has not been verified.

Choose your path

Build with models

Start with concepts, relations, metadata, packages, views, actions, and services.

• Conceptual programming
• Application models
• Tutorials

Build with code

Use SDKs and bindings over the same Runtime. The most complete binding documentation currently available is for .NET with C# and F#; additional bindings can be added without changing the overall site architecture.

• Bindings
• .NET runtime programming
• Public API

Integrate a Runtime

The programming model separates the public binding surface from the execution mode. Applications can target a local or remote Runtime without exposing engine implementation details in business code.

• Architecture
• Distributed architecture
• ABI

Work with knowledge

For conceptual models, hypergraphs, reasoning, and advanced mechanisms:

• Knowledge engineering
• Conceptual hypergraph
• Agents

Documentation depth

The site uses four levels of depth:

1. Orientation — find the right path.
2. Build — guides, tutorials, examples, and patterns.
3. Mastery — architecture, ABI, FPL/FPLN, distribution, security, and diagnostics.
4. Reference — APIs, formats, metadata, manifests, capabilities, and compatibility.

One product, two documentation roles

• logiCells.com is the discovery and product-orientation entry point.
• logiCells.net is the technical source for platform matrices, prerequisites, Runtime contracts, SDK/binding guidance and reproducible developer evidence.
• The canonical corporate claims policy is published on logiCells.com — Claims; this site applies that policy to technical documentation through Maturity and evidence.

Multi-language principle

Topics that belong to the Runtime or the logiCells model remain language-independent. C#, F#, Python, Rust, Java, Node.js, Go, and future binding-specific details are documented under their binding areas.

An example written in C# does not make the underlying concept .NET-specific.