blends

ACRYL BLENDS: pre-built whole-ACRYL-app definitions - undifferentiated "stem cells" to be specialized, evolved into new projects, and adapted to workflows.

A BLEND is a formal, versioned description of a complete pre-configured ACRYL application: the runtime plane and the starting Cordis plugin rows with their configuration, compilable directly to the Cordis composition the desktop Loader already understands.

• Two kinds share one manifest schema: kind: Blueprint (shareable starter, published to the hub) and kind: Blend (owned instance with lineage, lock, and evolution state; evolved Blends can be republished as Blueprints).
• The hub (acryl.dev/blends) catalogs both kinds, sibling to acryl.dev/packages and acryl.dev/store.

Repository map

• docs/ACRYL_BLENDS_SPEC.md - governing product spec (v0.1): manifest models, catalog, instantiation transaction, phases.
• docs/BLENDS-ROADMAP.md - milestones, locked decisions, architectural invariants, deferred areas.
• docs/workmethodology/ - the ACRYL hybrid engineering methodology used in this repo.
• specs/<NNN-feature>/ - Spec Kit feature ledgers: spec.md, research.md, plan.md, tasks.md. All planned work lives here.
• packages/ - implementation, starting with blends-core (parse, validate, resolve, compile).