Composition Playground v1¶

Explore the initial composition that the canonical Composition provider has already computed for a production recipe and explicit optional-component intent.

This page consumes published provider projections. It does not resolve dependencies, conflicts, ownership, or materialization rules in the browser.

v1 scope¶

The canonical include projection retains the bounded 2^N include-case table. Explicit exclusion is represented separately as provider-resolved single-component transitions rather than enumerating a 3^N state space. For WebMCP the UI therefore distinguishes Default, Adopt, and Explicitly exclude while preserving the Composer's existing include/exclude authority.

Parameters remain an empty object, mode remains initial, and the target repository remains empty. Existing-repository, update, and upgrade workflows are outside this page.

Both canonical projections are published by the pinned Composition provider as deterministic gzip-compressed JSON. The intent projection uses an indexed encoding: non-negative values reference canonical resolution outcomes; negative values reference provider-supplied canonical errors. Compression and indexing are transport details and do not move resolution logic into Site.

The displayed semantic source revision is the exact Composition revision recorded by the resolution projection. The displayed published Composition provider revision comes separately from Site's /build-provenance.json. The intent projection is accepted only when its semantic source revision and resolution projection identity match the loaded canonical resolution projection.

If a projection or Site build provenance is unavailable or malformed, the relevant interactive result fails closed instead of attempting browser-side dependency resolution.