Build for clients without losing control of change.
Scope, quote, deliver and evolve business applications with a clearer view of what each change affects.
logiCells Community is an executable conceptual runtime for developers and small teams building business applications. Keep business meaning, application structure, knowledge and execution connected — and expose that structure safely to agents and tools.
Community Alpha targets October 2026. Try the workflows early, report friction and help shape the developer experience.
Community Alpha is available. APIs, tooling and documentation may still change between releases.
Community is broader than one persona. Start from the problem you care about, then converge on the same models, tooling and runtime.
Scope, quote, deliver and evolve business applications with a clearer view of what each change affects.
Keep concepts, actions, views and runtime contracts aligned while a small team moves quickly.
Model concepts, relations, actions and boundaries as explicit application material instead of documentation that drifts.
Use H-Logic, provenance, scoped knowledge and governed actions instead of treating the application as opaque text.
Work with cell, VS Code and tooling contracts for repeatable workflows, CI and extensions.
Download a starter, open it in VS Code, change one thing and inspect what the runtime sees.
A class, table, form or endpoint may be produced later. The first level of meaning is conceptual: what exists, how it relates, what can happen and what constraints apply.
Name concepts, roles and relations in the language of the domain.
Add actions, views, services and application packages without making those technical surfaces the only home of meaning.
Use VS Code and cell to navigate, validate, inspect and plan changes through shared tooling contracts.
Compile and execute the application while keeping its conceptual structure available to developers, tools and governed agents.
Use VS Code for source-first editing and diagnostics, and cell for repeatable inspection, validation and automation. The editor does not become a second implementation of the platform.
# check the environment cell doctor # inspect the assembled application cell application inspect app.lgc # preview a change cell application compile plan app.lgc # run it cell server start app.lgc
Connect OpenClaw, another agent framework or your own automation through cell, Tooling endpoints or MCP. Semantic actions remain part of the application; policy, confirmation and execution stay owned by the runtime.
Learn the development loop before diving into the architecture. Mission-oriented starters come next as the community tells us what it builds most often.
Task, Project, relations, views, actions and a complete first runtime loop.
Customer, Contact and Opportunity published through a working service.
H-Logic, semantic queries and explanations over explicit business knowledge.
A client asks for “one small change.” The freelance landing path shows how a conceptual model and an impact plan can give you a concrete basis for understanding the scope before you commit.
Research notes and technical deep-dives around conceptual hypergraphs, governed agents and explainable application evolution.
Concepts, roles and multi-party relations as first-class application structure.
Read the noteGoverned capabilities and explicit semantic authority.
Read the noteUnderstanding impact, not only rebuilding faster.
Read the noteUse the runtime on real or realistic problems. Tell us what works, where you get stuck and which workflows would make logiCells more useful.