Skip to content
Browse documentation
start here

Capabilities and contracts

Understand capabilities, contracts, adapters, and native ownership without a universal Application facade.

Capabilities

A Smoothie application is your product, not a required Framework class or global Runtime. Import focused TypeScript capabilities for Service, Model, Agent, Tool, Worker, and Governance behavior. Whisk supplies interface semantics, styles, and renderer implementations. You can use one capability without starting the others. Workflow composition is currently shown in Recipes, not offered as a separate package.

Recipes show how capabilities fit together, in ordinary editable source rather than a new application language. Capability runtimes execute work; your native targets own the processes or requests in which that work runs. Keep importing and constructing a capability separate from starting a host or accepting external work.

Contracts

Contracts specify accepted data, results, events, and observable rules. Server and client can share a Service contract without the client importing server code. A Whisk catalog can constrain a generative UI document without making native JSX components interchangeable. Host-specific lifecycle and integration behavior stay in native code.

TypeScript is the current release scope. Language-neutral contracts guide future SDK projections, but do not promise other-language packages, matching APIs, or runtime parity.

Adapters

A Service adapter connects endpoint contracts to an HTTP host; a Model adapter connects inference to a provider; a Whisk adapter renders portable UI semantics with a native renderer. Choose only the integrations your application needs and that are qualified with your release. Importing an adapter does not provide authorization or production safety.

An adapter handles integration mechanics. Your application still owns policy, secrets, data access, external effects, and error handling. Native routers and build tools do not become Framework-wide abstractions merely because a Recipe uses them.

Source, packages, and metadata

Recipe sourceCopied once and edited as product source; package switching does not regenerate it.
Framework packagesPrepared, versioned archives retained with notices and release evidence.
smoothie.tomlProject/workspace identity and declared contracts; not credentials or a task graph.
Native manifestsDependency versions, lockfiles, scripts, compiler and host configuration.
CLI evidencePlans, selected artifacts, checks, and recovery records; not inferred application health.

Execution and authority

The CLI inspects metadata without starting your application. Native operations you explicitly request can run your scripts or contact providers, and reviewing a plan does not apply it. An MCP connection for a coding agent does not receive your product's runtime authority. Configure credentials and approve effects where they are actually used.

Read Compatibility before choosing a host or rendering mode, and Develop with a coding agent before giving an external agent local context or executable tools.