Capability

Compose bounded contexts into one organisational model.

Build small domain models independently across architecture, brand, identity, and estate verticals. The loader merges them by key; scoped IDs catch collisions before runtime.

What it is

For the Blueprint architecture service, composition joins the YAML files of a declared model into a queryable graph. Scoped identifiers and typed references connect bounded contexts without requiring one giant file. Archally also has schemas for other domains; storing them together does not establish semantic federation. Meaningful cross-schema composition requires explicit semantic mappings and consumer adaptations. The supported Blueprint boundary here is file loading, references and identifier checks; conceptual-conflict detection still needs domain review.

Context map of the PrestaShop model, with twelve bounded contexts, their services and dependency edges.
Architecture map. A map of bounded contexts and modeled dependencies makes the composed Blueprint visible. It is not evidence of federation between schemas. Static preview of the sample shop model.

Built on

  • YAML files grouped into a declared Blueprint model
  • Scoped identifiers and typed cross-file references
  • Schema checks, reference integrity and specified semantic rules
  • Strategic classification of a bounded context's business role and modeling characteristics
  • Explicit mappings and consumer adaptations when another schema is involved

How it works

Author the selected bounded contexts in YAML. Load the declared Blueprint model and run schema, reference and semantic checks. Duplicate identifiers and unresolved references are specified validation concerns; deciding whether two concepts mean the same thing still needs a domain review. Strategic context classification records business role, evolution and modeling characteristics. Compare supported baseline, proposed and historical model states separately from observed runtime behavior.

Software Design board of the orders context, opening on Place an order with its actors, command, event and hotspots.
Orders in Software Design. The Order board focuses the same model on commands, rules and events for domain review. Validation does not settle conceptual disagreements. Static preview of the sample shop model.