Compose from a product blueprint
blueprintStart from a real product shape with a host, services, modules, local processes, and Launchpad state already connected.
Leverages
lenso app compose ./acme-support --blueprint support-desk --applyLenso is the modular app framework for composing real product shapes, verifying every change, and evolving stable boundaries into services.
Start with a product blueprint, add reusable business capabilities, verify the generated system, and split services only when their boundaries are ready.
Start from a real product shape with a host, services, modules, local processes, and Launchpad state already connected.
Leverages
Add modules, services, addons, or team-owned capability packs through a reviewable App Change Plan.
Leverages
Doctor, App Proof, contracts, checks, and Console turn generated state into evidence humans and agents can review.
Leverages
Keep one deployable app while boundaries are changing, then move selected capabilities into independently delivered services.
Leverages
App Composer, module manifests, service contracts, Console, and agent workflows all read from the same explicit system model.
Runtime
The generated product shape teams actually run.
Generated app
A runnable host, service workspace, system graph, and Launchpad state from one product blueprint.
Module manifest
Explicit routes, data, actions, lifecycle, dependencies, and console surfaces.
Capability packs
Reusable product slices that can carry modules, services, docs, and agent context.
Console
Inspect App Lifecycle, modules, service state, runtime stories, and operational evidence.
Agent rails
Bounded planning, generation, checks, proof, and concrete next actions.
Evidence
Where the same facts become reviewable and actionable.
App Lifecycle
Inspect what the host actually loaded, catch readiness gaps, review App Proof, and copy the next concrete command from one operator workspace.
See the whole appServices, modules, addons, and capability packs.
Find the gapDoctor, drift, blocked plans, and missing proof.
Take the next stepCommands and evidence that humans and agents can review.

App Lifecycle in Console — the generated app, its readiness, proof, and next action in one view.
Lenso gives humans and coding agents bounded plans, explicit contracts, recoverable changes, and evidence instead of hidden framework magic.
Begin with a working business-system shape instead of an empty host and a list of infrastructure choices.
Routes, actions, data, events, service dependencies, and operator surfaces stay named and inspectable.
Plans, Doctor, App Proof, contract checks, and Console make generated changes reviewable.
Carry reusable business slices across modules, services, documentation, and bounded agent handoffs.
See App Lifecycle, installed modules, service state, runtime stories, data surfaces, and delivery evidence.
Build modular first, then move stable boundaries into independently delivered services without rewriting the product model.