Configuration reference
Look up schema-1 project/workspace fields and the native tools or capability APIs that own other configuration.
Project manifest fields
smoothie.toml schema 1 describes project identity and local contracts, not runtime configuration. Each manifest declares exactly one of [project] or [workspace].
A project needs an SDK, a contract export, or both. The parser also recognizes python, go, rust, elixir and zig; recognition does not promise SDK support. A project may stand alone or be an explicit workspace member.
Workspace fields and validation
Unknown schema-owned fields are rejected. Member paths and project names must be unique; contract sources stay inside their exporting project. Local imports must resolve to one compatible export. The manifest reader accepts at most 1 MiB of UTF-8 input.
For a minimal manifest and validation steps, use Configuration and environment. Project operations explains metadata inspection and native verification.
Configuration outside smoothie.toml
There is no Framework-wide Config object or runtime-profile registry. Find capability options through the SDK package map; use native tool configuration for builds and dependencies.
Environment values and secrets
There is no global Framework environment-variable namespace or implicit dotenv loader. Each target or adapter documents the values it consumes. Browser build variables are public bytes; credentials belong in the server environment or native secret store. See Keep secrets server-only for the procedure.