Soustack Toolchain

The Soustack toolchain is a set of complementary components that support authoring, validating, ingesting, and consuming Soustack recipes. Each tool has a clearly defined role, and none are required to adopt Soustack.

Core concepts

Soustack is a data contract first: the specification defines the shapes and guarantees, and the tools build on top of it. Each component is optional and composable, so adoption can start with raw JSON and grow into richer integrations as needed.

The toolchain

1. The Foundation

soustack specification

The canonical source of truth for schemas and contracts. All normative guidance lives in the specification at spec.soustack.org.

2. The Engine

soustack core

Reference implementation for validation, computation, and capability handling. It enforces the specification and provides reusable primitives for builders. View the repository.

soustack ingest

Parsing and converting external recipe formats into Soustack. It is optional and pipeline-oriented, so teams can ingest legacy content without changing their source systems. View the repository.

3. The Interface

soustack blocks

UI primitives for rendering Soustack recipes. Blocks focus on presentation and interactivity, leaving data definition to the specification and core. View the repository.

soustack embed

Drop-in embedding for publishers who want minimal integration effort. It is the lowest-friction adoption path when you want to surface recipes without wiring a full stack. View the repository.

4. The Intelligence

soustack mcp

Agent and tool interfaces for programmatic access to Soustack data. It targets experimental and advanced usage where automated systems consume or act on recipes. View the repository.

---

How to choose what you need

You can adopt Soustack without any tooling: the data contract stands on its own. Common starting points include using soustack core for validation, soustack ingest to import legacy content, and soustack blocks or soustack embed to render recipes. Each component can be combined or ignored as your product requires.

What this site is (and is not)

soustack.org explains the ecosystem and adoption paths, while spec.soustack.org remains the sole source of truth for the specification. This page is narrative and explanatory, not normative.