Presolve
Developer Preview

Current status.

Presolve is under active development. This page separates implemented architecture and public evidence from things the project still does not claim.

Implemented

Portability core

  • Application Contract 0.1
  • Environment Specification 0.1
  • Deterministic compatibility resolver
  • Symbolic DeploymentPlan
  • Stable EnvironmentId + ProviderId identity
  • Required/preferred feature negotiation
  • Node-side provider realization boundary
Read the architecture
Implemented

Capability semantics

  • presolve:kv/store@0.1.0
  • presolve:objects/store@0.1.0
  • presolve:sql/database@0.1.0
  • presolve:queue/work-queue@0.1.0
  • WIT/runtime bindings for current Component capability paths
  • Reusable provider conformance harnesses
Capability reference
Implemented

Providers + execution

  • WebAssembly Component workloads
  • OCI/container workload identity + execution path
  • Docker local executor
  • Memory KV/object/queue providers
  • Redis KV adapter over RESP/TCP
  • Cloudflare Workers KV adapter
  • S3-compatible object adapter
  • SQLite + PostgreSQL SQL adapters
Implemented

Developer workflow

  • presolve build
  • presolve inspect source + release views
  • presolve check
  • presolve plan
  • presolve env … environment management
  • presolve dev local workflow
  • Versioned JSON projections
  • Rust + TypeScript authoring paths
CLI guide
Public proof suite

Same-release evidence now covers three provider families plus queue runtime semantics.

SliceProviders/environmentsStatus
KVmemory · Redis · Cloudflare KVsame-release portability proven
Object storagememory · S3-compatiblesame-release portability proven
Relational SQLSQLite · PostgreSQLconformance + same-release portability proven
Work queuein-memory leased queuefull capability/runtime proof; second provider next
Public proof pageDetailed evidence
Not a guarantee

Not stable yet

  • Stable CLI/schema/SDK compatibility
  • Production-grade cloud-provider support
  • Arbitrary workload portability
  • Automatic infrastructure provisioning
  • Native executable workload class
  • Full deployment lifecycle/control plane
Next

Broaden queue substitution and semantic precision.

The next queue milestone is a materially different network/managed provider so the exact same queue release can be exercised across providers, as KV, objects, and SQL already are.

Real provider differences are also building evidence for richer typed semantic properties such as limits, retention, lease ranges, and other values that do not fit boolean feature flags.

Queue proofSemantic limits