1
Compose
lenso.app.jsonMaterialize the exact app revision, artifact digests, dependency selections, and linked or service-backed bindings.
Leverages
Product Blueprints
Agent-ready Rust
business systems
$
lenso app compose ./support-desk --blueprint support-desk --applyLenso is the Rust modular application and microservice framework for composing a real product, running it locally, and evolving stable boundaries.
Compose, Run locally, Connect, Status
Materialize one app composition, run and connect it through the public local entrypoint, then read direct object status in Console.
Product Blueprints2
Run locally
dev upRun lenso dev up with --console-root to start the Host, auto-start Services, and the independent Console in one foreground-bound local session.
Leverages
Connected local path3
Connect
dev upThe same command creates signed loopback enrollment material, reconciles Module-owned UI artifacts, and connects the exact topology. Console does not deploy or adopt the app.
Leverages
Console4
Status
connectedRead direct connection state for each System object, then inspect and control supported local Workloads through their separate operational state.
Leverages
System statusFrom authoring inputs to a connected System
Blueprints and Capability Packs materialize one exact App Composition; Agent Skills guide the bounded authoring path. Console then projects the connected System's services, modules, adapters, workloads, and Surfaces.
Explicit product model
The materialized app and owner-local contracts keep composition, APIs, and Console Surfaces explicit.
App Composition
One content-bound selection of Module Releases, dependencies, and implementation bindings.
Module manifest
Explicit Business API operations, runtime behavior, dependencies, and Console Surfaces.
Business API
Generated clients call declared module operations through scoped Surface Grants.
Console
Connect an exact System, load receipt-bound Surfaces, and report direct object states.
Service tiers
Provider and Autonomous Service contracts make ownership and language support explicit.
System status
Where the same facts remain observable and actionable.
Connected System
System IDTopology DigestConnection StatusServicesModulesWorkloadsControl AdaptersManagement BindingModule SurfacesSurface Grants
Console reports the connected System
The images below are illustrative mock views, not current product captures. The shipped Console reads exact topology, Module-owned Surfaces, direct object status, and supported local Workload operations.
See the whole appServices, modules, Workloads, Adapters, and capability bindings.
Find the gapEvery unavailable, incompatible, or unmanaged connection projection includes a direct reason.
Take the next stepBrowser actions use Console Service and never receive direct Service credentials.
Illustrative Runtime Stories mock — use the shipped Story workbench to inspect correlated runtime records.
Illustrative operations mock — queue pressure, failures, and dead-letter signals are example data, not a live Console capture.
Built to make change reviewable
Lenso gives humans and coding agents explicit contracts, bounded actions, direct status, and recoverable local operations instead of hidden framework magic.
compose
run_local
connect
status
control
Product blueprints
Materialize the initial exact App Composition, then remain only as informational provenance.
app: support-deskComposedjson
system: support-deskRunninglocal
consoleConnectedsystem
module contractsCurrentlock
surface: support-ticketsConnectedmodule
service: support-suite-providerRunningservice
runtime storiesRunninglive
local controlConnectedadapter
workloadRunningstate
next actionAvailableagent
Explicit contracts
Business APIs, events, service dependencies, and operator surfaces stay named and inspectable.
Authoring inputs
Product BlueprintsCapability PacksAgent SkillsOwner-local contracts
Module ContractsBusiness APIsService ContractsConnected runtime
ServicesModulesWorkloadsControl Adapters
Public lifecycle
Compose, Run locally, Connect, and Status keep every developer and operator on the same path.
Capability packs
Materialize reusable business slices into the App Composition instead of becoming parallel runtime state.
Console
See the connected System, module Surfaces, direct object states, runtime stories, and local workload operations.
Service-ready evolution
Build modular first, then move stable boundaries into independently delivered services without rewriting the product model.