Next

This is the current-development manual for Minco: a contract-to-cloud Rust framework for low-idle-cost web applications on AWS. It documents the source on main; it never changes the meaning of the stable 1.0.0 documentation.

The manual is organized progressively: begin with one working application, then reach for focused guides, the component catalog, practical recipes, or exact reference when you need them.

Build an applicationUnderstand the contract-to-cloud path, project layers, and development loop.Use resource APIsImplement create, list, read, update, and delete with one client-facing convention.Author a pluginPackage a statically linked plugin and exercise the public conformance boundary.Develop with coding agentsInstall version-matched Codex and Claude skills and inspect bounded project context.Operate on AWSReview Plan IR, residual cost, exact artifacts, and mutation evidence.Browse all featuresSee the framework surface by contract, data, runtime, deployment, and evidence plane.Choose built-in pluginsCompare all 18 plugins, adapters, and runtimes by purpose, stability, and cost behavior.Follow practical recipesCombine the pieces for CRUD, background work, feedback, files, and safe AWS delivery.

What Is Documented Here

Area	Current development boundary
HTTP resources	JSON data envelopes, bounded cursor pages, strong entity tags, and Problem Details
Plugins	Archive-visible distribution metadata and public offline conformance reports
Realtime	Subscriber-only AppSync invalidation with authoritative HTTP resynchronization
Local AI	Bounded ProjectView, read-only MCP, and accessible workbench projections
Agent development	Version-matched skills, digest-bound client projections, bounded context, and deterministic evaluation
Testing	Domain, application, adapter, HTTP, plugin, deployment, and release evidence remain distinct
AWS	Zero provisioned application compute, explicit DynamoDB access patterns, and visible residual managed-service cost

The Golden Path

new -> contract -> generate -> dev -> migrate -> seed -> test -> inspect
    -> package -> change set -> migrate target -> deploy -> verify
    -> promote exact artifact -> observe or compatibility-checked rollback

Each arrow is explicit and inspectable. Minco does not add a runtime service locator, Active Record layer, hosted control plane, hidden scheduler, or boot-time production migrations.

Popular Topics

• Install Minco and build the first application.
• Use typed configuration, database lifecycle controls, and graph-driven local development.
• Add identity and sessions, events and notifications, files and static sites, or the realtime invalidation path, client feedback loop.
• Inspect the same bounded project model through ProjectView, MCP, and the local workbench, or select the DynamoDB Orders adapter.
• Set up Codex and Claude Code with project-local, version-matched Minco workflows.
• Review the complete feature catalog, built-in component catalog, and Cargo feature reference.

Start with the framework tour, browse the exercised examples, or go directly to the current CLI reference.