Getting Started: from zero to a running model

Documentation status: guide. This path only claims steps that are backed by a published Runtime or declarative contract.

This is the entry point for a developer who has no preconfigured logiCells environment. The target is deliberately concrete: establish the platform boundary, validate the Runtime, start one supplied application configuration, observe the expected loading checkpoints, and only then create or edit model metadata.

Fast paths

• Prerequisites
• Platform matrix
• First verified run
• Project conventions
• All tasks

Recommended order

1. Prerequisites and installation contract
2. Platform matrix
3. First verified run
4. First project conventions
5. Declarative developer guide
6. .NET binding

First-success rule

Do not ask a new developer to diagnose a model before the Runtime boundary is known to work. A useful first success is a visible startup sequence that reaches application loading, package loading, manifest/model compilation, semantic initialization, and Runtime start.

The documentation does not invent a download URL or installer command when the release source does not certify one. Release-specific installation instructions must name the artifact, version and supported platform before they can be marked as reference.