You do not need to understand Presolve's internal terminology before using it. The shortest path is: install the released CLI, follow the first-run tutorial, learn the core commands, then read deeper reference material only when a concept becomes relevant.
Run one complete workflow.
The getting-started tutorial uses the repository's KV example and takes you through the entire local developer loop without requiring Redis, PostgreSQL, S3, Cloudflare credentials, Docker, or a source build of Presolve itself.
Use the published native CLI for your platform. Building Presolve from source is a contributor path, not a prerequisite.
See what Presolve thinks the application needs before choosing infrastructure.
Declare the runtime and services available on your machine.
Create the .presolved release and evaluate that application against the environment.
Realize the selected local provider and execute the component.
Think in questions, not Presolve vocabulary.
presolve inspect — What does Presolve think my app needs?See the application definition without selecting any infrastructure.
presolve build — What exact build am I shipping?Create a .presolved package that does not contain environment-specific choices.
presolve check — Can this environment run it?Verify compatibility before execution. If it cannot run, Presolve explains what is missing.
presolve plan — What will it actually use?Inspect the runtime and provider selections Presolve made for this environment.
See installation, commands, output, JSON automation, diagnostics, and local development →
The names are less important than what each one answers.
presolve.tomlWhat is this application, and what does it need in order to run?
A place it can runpresolve.env.tomlWhat runtimes, services, and resources are available in this environment?
The thing you shipapplication.presolvedThe packaged application produced by presolve build. It stays the same when you evaluate another environment.
What Presolve selected when it matched one application build to one environment.
Choose the task you are trying to complete.
Install Presolve, then follow one complete local workflow with explanations and troubleshooting.
02 · OperateCLI & workflowsInstall, build, inspect, check, plan, run locally, manage environments, and use machine-readable output.
03 · AuthorDefine your applicationDescribe workloads, required services, resources, topology, and network intent.
04 · TargetDefine an environmentDescribe what an environment can execute and which providers it makes available.
05 · DistributeBuilt releasesUnderstand what goes into .presolved and why environment configuration stays out.
Understand portable contracts for KV, objects, SQL, queues, and future services.
07 · UnderstandArchitectureRead the formal application/environment/provider/resolution model once the workflow is familiar.
08 · VerifyProofsRun the same-build portability checks and inspect exact evidence.
Current proofs cover several kinds of infrastructure.
kv/storememory · Redis · Cloudflare KVsame buildobjects/storememory · S3-compatiblesame buildsql/databaseSQLite · PostgreSQLsame buildqueue/work-queueleased in-memory providercapability proofTranslate the jargon back to these simple ideas.
| Technical term | Plain meaning |
|---|---|
| Application Contract | the file describing your app and what it needs |
| Environment Specification | the file describing what a target environment can provide |
| Capability | a service or behavior your app needs, such as key-value storage or SQL |
| Provider | the concrete implementation that supplies a capability |
| Resolution | checking compatibility and choosing matching providers |
| DeploymentPlan | the recorded result of those choices |
| Immutable release | the same packaged application build, unchanged between environments |
The website teaches the workflow; the repository carries the full technical record.
Deep implementation details, canonical schemas, diagnostics, and development checkpoints remain in the repository for auditing and contributor work.