Choose a tool for your question

Public Blueprint resources and Archally Pro tools: what they help you answer, what is available and how to get it.

Public Blueprint resources

These selected resources are available from the public Blueprint repository under the licences shown. Follow the linked instructions to use them locally.

Licensing overview

Apache-2.0

Blueprint reference schema

Which question does it answer? Which concepts and relationships can I model?

For: Model authors defining concepts and relationships.

Use when: Choosing what to record in a Blueprint model.

Bring -> get: Modeling needs -> schema definitions.

An excerpt of the Blueprint domain schema file: its title and description, then the start of the operation definition with its required id and kind and the four operation kinds.Open full-size picture

Apache-2.0

Validator

Which question does it answer? Does this model conform to its schema, and do its references resolve?

For: Model authors checking conformance and references.

Use when: Before sharing a model or after editing it.

Bring -> get: Blueprint model -> schema and reference findings.

A terminal running the public validator on the PrestaShop model: 173 files validated, no schema or cross-reference errors, one gap warning, PASSED.Open full-size picture

FSL-1.1-ALv2

Semantic checker

Which question does it answer? Which modeling gaps remain beyond schema validity?

For: Model reviewers finding relationship gaps.

Use when: After schema validation, before reviewing model completeness.

Bring -> get: Blueprint model -> modeling warnings and notes.

A terminal running the semantic checker on the PrestaShop model: 93 rules over 3883 entities and 9389 relations, the first modeling warnings, and the summary of 341 warnings and 703 notes.Open full-size picture

FSL-1.1-ALv2

Schema updater

Which question does it answer? How can I move a model between supported schema versions?

For: Model maintainers moving between schema versions.

Use when: Before adopting a supported schema version.

Bring -> get: Existing model -> migration preview or updated model.

A terminal previewing a schema update of the ecommerce model from v2.6 to v2.8 without changing it: the chain of 15 hops, each with the change it plans.Open full-size picture

Apache-2.0

Modeling kit

Which question does it answer? How can I begin modeling with an AI agent?

For: Model authors guiding an AI modeling agent.

Use when: Starting or extending a Blueprint model with an agent.

Bring -> get: Modeling task -> agent instructions and modeling guidance.

A terminal listing the modeling kit: one blueprint modeler agent, two commands and fifteen modeling skills.Open full-size picture

FSL-1.1-ALv2

Public Blueprint renderer

Which question does it answer? How can I generate a Markdown report with Mermaid diagrams from my model?

For: Model authors sharing a readable model overview.

Use when: Preparing a Markdown report for review.

Bring -> get: Blueprint model -> Markdown with Mermaid diagrams.

On the left, a terminal confirming that the generated overview of the PrestaShop model is up to date; on the right, the start of that Markdown overview with its Mermaid context map source.Open full-size picture

Renderers

Renderers are programs that produce diagrams and reports, convert diagrams or stamp provenance. bp render is the CLI command that runs them from a project's render manifest. Choose by the question you need to answer.

Available now. Access and delivery agreed for the selected scope.

How is the system connected?

  • arch-map

    Which question does it answer? Draws bounded contexts, ownership and service integrations.

    For: Architects reviewing context ownership and integrations.

    Use when: Agreeing service boundaries and dependencies.

    Bring -> get: Blueprint model -> architecture map.

    Architecture map of the PrestaShop model: twelve bounded contexts with their kind, services and owners, joined by typed dependency and traffic lines, with the legend below.Open full-size picture
  • c4-map

    Which question does it answer? Draws system context and container diagrams with their connections.

    For: Architects explaining system structure.

    Use when: Reviewing system context and containers.

    Bring -> get: Blueprint model -> C4 context and container diagrams.

    C4 container diagram of PrestaShop: the people who use the system above, the services inside the system boundary below, with the operations each person initiates.Open full-size picture
  • service-surface

    Which question does it answer? Draws service calls and messages through contracts, brokers and channels.

    For: API developers reviewing calls and messages.

    Use when: Agreeing how services communicate.

    Bring -> get: Modeled service contracts and channels -> service surface map.

    Part of the service surface map: PrestaShop services with their contracts and channels, joined by HTTP and in-process call lines labelled with what they carry.Open full-size picture
  • strategy-grid

    Which question does it answer? Places bounded contexts by declared kind, evolution and business model role.

    For: Architects assessing context strategy.

    Use when: Discussing a context's kind and evolution.

    Bring -> get: Declared context classifications -> strategy grid.

    Strategy grid of the twelve PrestaShop bounded contexts, placed by kind (core, support, generic) and evolution (genesis to commodity).Open full-size picture
  • infrastructure-map

    Which question does it answer? Draws infrastructure resources, environments, deployment scopes and bindings.

    For: Platform engineers reviewing deployments.

    Use when: Checking resource and environment bindings.

    Bring -> get: Modeled infrastructure -> infrastructure map.

    Infrastructure map of PrestaShop: web host, database, cache, media store, application and mail transport with how they connect, the three environments and the legend.Open full-size picture

Who needs what, and why?

  • goal-map

    Which question does it answer? Draws goals, their measures and the work that advances them.

    For: Product owners connecting work to goals.

    Use when: Checking which work advances a measured goal.

    Bring -> get: Modeled goals and measures -> goal map.

    Goal map of PrestaShop: critical and high goals in rows, each with the KPI that measures it and the capabilities, value streams and leverage points that advance it.Open full-size picture
  • capability-map

    Which question does it answer? Draws business capabilities, maturity and ownership.

    For: Business architects reviewing capabilities.

    Use when: Discussing capability maturity and ownership.

    Bring -> get: Modeled business capabilities -> capability map.

    Capability treemap of PrestaShop: three top-level capability areas divided into their capabilities, each tile marked with its maturity.Open full-size picture
  • value-stream-map

    Which question does it answer? Draws value stream stages, actors, supporting capabilities and measures.

    For: Process owners reviewing value delivery.

    Use when: Agreeing stages, actors and supporting capabilities.

    Bring -> get: Modeled value streams -> value stream map.

    Value stream map: the Shop and Buy and Sell and Fulfill streams with their stages in columns and a lane per actor showing where each acts.Open full-size picture
  • persona-index

    Which question does it answer? Lists actors and personas with their goals, pain points and use cases.

    For: Product teams reviewing user needs.

    Use when: Checking whose goals a use case serves.

    Bring -> get: Modeled actors and personas -> persona index.

    Persona cards for PrestaShop actors: each persona with its description, goals, pain points and the use cases the actor takes part in.Open full-size picture
  • journey-map

    Which question does it answer? Draws the recorded emotions and friction along each use case.

    For: Designers reviewing experience and friction.

    Use when: Discussing a use case's recorded emotional journey.

    Bring -> get: Modeled use cases and emotions -> journey map.

    Journey map of the Add to Cart use case: four steps across the top, the shopper's emotion at each step on a five-level scale, and one branch for an out-of-stock product.Open full-size picture
  • story-board

    Which question does it answer? Draws story status and story point boards by actor, release or use case.

    For: Product owners reviewing story progress.

    Use when: Planning work by actor, release or use case.

    Bring -> get: Modeled stories and status -> story board.

    User story board of PrestaShop: a row per actor and a column per story status, with story counts and points in each cell and totals below.Open full-size picture
  • use-case-catalog

    Which question does it answer? Draws use case cards, actor relationships and scenarios.

    For: Analysts reviewing user scenarios.

    Use when: Agreeing actors and use case scope.

    Bring -> get: Modeled use cases -> use case catalog.

    Use case diagram of PrestaShop: actors drawn as figures beside each context's use cases, with the counts of stories and processes per use case.Open full-size picture

How does the work flow?

  • process-catalog

    Which question does it answer? Lists business processes from trigger to outcome, with their actors and sequences.

    For: Process owners reviewing workflows.

    Use when: Comparing process triggers and outcomes.

    Bring -> get: Modeled processes -> process catalog.

    Business process catalog page: 27 processes in 10 slices, with a filter, and a table of each process with how it starts, its phases, how it ends and its use cases.Open full-size picture
  • process-bpmn

    Which question does it answer? Draws business processes as BPMN diagrams and interchange files.

    For: Process analysts communicating workflows.

    Use when: Reviewing process lanes and flow in BPMN.

    Bring -> get: Modeled processes -> BPMN diagrams and interchange files.

    BPMN viewer page for the Place an order process, fitted to view: a process list on the left and the whole BPMN diagram with lanes for the order application, shopper, shop operator and payment module, from the cart check through the review steps to creating the order and applying its initial state, with the open risks and inquiries below.Open full-size picture
  • story-visualizer

    Which question does it answer? Draws story sequences and UML use case diagrams.

    For: Analysts explaining story interactions.

    Use when: Reviewing a story's sequence and actors.

    Bring -> get: Modeled stories -> sequence and use case diagrams.

    Sequence diagram of the shopper cart journey: the shopper's add, update and remove cart operations and the events they produce, with activity boundaries.Open full-size picture
  • event-storming

    Which question does it answer? Draws Event Storming boards across discovery and software design levels.

    For: Workshop facilitators exploring domain behavior.

    Use when: Discussing events, rules and discovery gaps.

    Bring -> get: Blueprint model -> Event Storming boards.

    Event Storming big picture of the Checkout slice: actors, events, rules, hotspots and goals as coloured sticky notes along the cart journey and discount setup.Open full-size picture
  • event-storming-stories

    Which question does it answer? Draws Process Modelling and Software Design boards for each story.

    For: Engineers refining story behavior.

    Use when: Reviewing a story's commands, events and policies.

    Bring -> get: Modeled stories -> Process Modelling and Software Design boards.

    Process modeling board for the shopper cart journey: actor, commands and events in flow order, with the policies and hotspots attached to them.Open full-size picture
  • communication-diagram

    Which question does it answer? Draws process messages between participating services.

    For: Engineers reviewing service messages.

    Use when: Checking the recorded communication in a process.

    Bring -> get: Evidenced process messages -> communication diagram.

  • sequence-states

    Which question does it answer? Draws use case sequences across current, migration and planned model states.

    For: Engineers comparing use case states.

    Use when: Reviewing current, migration and planned interactions.

    Bring -> get: Modeled use case states -> sequence diagrams.

    Sequence states page for the Add to Cart use case: the AS-IS sequence between the shopper and the checkout service, with its out-of-stock alternative.Open full-size picture

What is evidenced, constrained or at risk?

  • risk-map

    Which question does it answer? Draws a likelihood and impact matrix with a risk register and mitigations.

    For: Risk owners reviewing exposure and mitigation.

    Use when: Prioritizing recorded risks for review.

    Bring -> get: Modeled risks -> likelihood and impact matrix and register.

    Risk matrix of PrestaShop: risks placed by likelihood and impact, the cells coloured by exposure, each risk marked as measured, inferred or assumed.Open full-size picture
  • nfr-register

    Which question does it answer? Draws quality requirements, their constraints and the checks that guard them.

    For: Quality engineers reviewing constraints.

    Use when: Agreeing quality requirements and their checks.

    Bring -> get: Modeled quality requirements -> NFR register.

    NFR register of PrestaShop: 68 quality requirements grouped by characteristic (security, compliance, resilience and not stated) and by discovery stage.Open full-size picture
  • traceability-matrix

    Which question does it answer? Draws which requirements have test cases and where coverage is missing.

    For: Test leads reviewing requirements coverage.

    Use when: Finding requirements without test cases.

    Bring -> get: Modeled requirements and test cases -> traceability matrix.

    Traceability coverage of PrestaShop: for rules, transitions, operations and concepts, a bar of how many are validated by two or more, one or no test cases.Open full-size picture
  • test-cases-pdf

    Which question does it answer? Produces a test dossier with story flows, architecture and coverage.

    For: Test leads preparing a test review.

    Use when: Sharing story flows and coverage for a slice.

    Bring -> get: Modeled test cases -> test dossier.

    Test case report for the Checkout slice: the share of operations, rules, transitions and processes covered by test cases, and how many tests are automated.Open full-size picture
  • feature-evidence

    Which question does it answer? Draws feature evidence and gaps across model and code references.

    For: Product teams reviewing feature evidence.

    Use when: Checking model and code reference gaps.

    Bring -> get: Modeled features and code references -> feature evidence matrix.

    Feature evidence matrix: PrestaShop capabilities in rows and value stream stages in columns, each bar counting the operations that support it.Open full-size picture
  • adr-register

    Which question does it answer? Produces a decision register and individual Architecture Decision Records.

    For: Architects reviewing decision history.

    Use when: Explaining which decisions stand or were superseded.

    Bring -> get: Modeled decisions -> register and Architecture Decision Records.

    Architecture decision register of PrestaShop: ten decisions grouped by month with status, scope and title, and the line showing which decision supersedes which.Open full-size picture
  • governance-ledger

    Which question does it answer? Lists open inquiries, assumptions, trade-offs and non-goals.

    For: Review leads tracking unresolved knowledge.

    Use when: Reviewing inquiries, assumptions and trade-offs.

    Bring -> get: Modeled governance records -> governance ledger.

    Governance ledger page: 19 inquiries, 14 assumptions, 11 trade-offs and 15 non-goals, with a filter and the open inquiries grouped by domain.Open full-size picture

What changes next, and what can I share?

  • leverage-map

    Which question does it answer? Draws ranked improvements, their dependencies and delivery timeline.

    For: Product owners prioritizing improvements.

    Use when: Comparing improvements and what they advance.

    Bring -> get: Modeled improvements and dependencies -> leverage map.

    Leverage map of PrestaShop: ranked improvements on the left, the goals and value streams each advances in the middle, and the watchlist on the right.Open full-size picture
  • roadmap-gantt

    Which question does it answer? Draws milestones and work items on an operational or strategic timeline.

    For: Delivery leads reviewing timing and progress.

    Use when: Discussing milestones and blocked work.

    Bring -> get: Modeled roadmap -> operational or strategic Gantt.

    Delivery roadmap Gantt of PrestaShop: releases and work items on a sprint timeline with milestones, progress and one blocked release.Open full-size picture
  • roadmap-description

    Which question does it answer? Describes what each roadmap milestone and work item delivers and why.

    For: Delivery leads explaining planned outcomes.

    Use when: Sharing what milestones deliver and why.

    Bring -> get: Modeled roadmap -> milestone and work item descriptions.

    Roadmap description page: what each release milestone and work item delivers, with a summary table of milestones, target dates and status.Open full-size picture
  • topic-impact-map

    Which question does it answer? Produces a change topic dossier linking findings, architecture and planned work.

    For: Change leads reviewing a proposed topic.

    Use when: Connecting findings to architecture and planned work.

    Bring -> get: Change topic and Blueprint model -> topic dossier.

    Topic impact dossier for the public PrestaShop inquiry orders.INQ001, Should PrestaShop migrate cart rules to a dedicated rules engine?: its text, the process, operation and concept it affects, the two goals and the risk it names, and the Orders bounded context it touches.Open full-size picture
  • brs-dossier

    Which question does it answer? Produces a business requirements specification from the model.

    For: Business analysts sharing business requirements.

    Use when: Reviewing business goals and requirements.

    Bring -> get: Blueprint model -> business requirements specification.

    Business requirements specification, Business goals chapter: goal counts and the goal map placing each goal by priority and discovery stage.Open full-size picture
  • strs-dossier

    Which question does it answer? Produces a stakeholder requirements specification from the model.

    For: Analysts sharing stakeholder requirements.

    Use when: Reviewing stakeholder needs and scope.

    Bring -> get: Blueprint model -> stakeholder requirements specification.

    Stakeholder requirements specification, Personas chapter: a table of actors with their persona, goals, pain points and use cases.Open full-size picture
  • product-document

    Which question does it answer? Produces a product area document from its modeled requirements and behavior.

    For: Product owners preparing a product brief.

    Use when: Agreeing goals, requirements and measurement.

    Bring -> get: Blueprint model -> product document.

    Checkout product document: the PM brief and the goals and measurement section, with the first goal's measure, capabilities and threats.Open full-size picture
  • mermaid-svg

    Which question does it answer? Converts generated Mermaid sources into SVG: sequence diagrams of process stories and use cases, flowcharts of process stories, C4 context and C4 container diagrams.

    For: Documentation authors preparing diagram files.

    Use when: Publishing supported Mermaid diagrams as SVG.

    Bring -> get: Mermaid sources -> SVG diagrams.

    A Mermaid sequence diagram converted to SVG: the Place Order use case between the shopper and the order service, with its stock and payment alternatives.Open full-size picture
  • artifact-stamp

    Which question does it answer? Adds provenance footers to generated artifacts; it draws no new diagram.

    For: Documentation owners identifying artifact provenance.

    Use when: Delivering artifacts with their model and build context.

    Bring -> get: Rendered artifacts -> provenance-stamped artifacts.

    The bottom of a rendered architecture map, enlarged: the provenance footer naming the model, its version, the generation time, the renderer and the build.Open full-size picture

Contract generator

An Archally contract models what a service exposes and consumes in the blueprint. The contract generator emits external syntaxes: OpenAPI, AsyncAPI, Arazzo, OpenRPC and Pact, including Pact consumer contract tests.

Available now. Access and delivery agreed for the selected scope.

Contract generator

Which question does it answer? Which external contract files can I generate from modeled service interfaces?

For: API developers sharing service interfaces with consumers.

Use when: Handing off interfaces or refreshing integration descriptions.

Bring -> get: Blueprint model -> OpenAPI, AsyncAPI, Arazzo, OpenRPC and Pact files.

Two generated contracts side by side: a Pact consumer contract between AdminApiClient and OrderService for updating an order return's state, and the OpenAPI operation for the same path.Open full-size picture

Pact consumer contract tests describe interactions expected by a calling application. Align the generated Pact with the consumer; the provider still verifies the contract.

Viewers

Explore a Blueprint model interactively. Connected viewers can use the GraphQL server; standalone builds use exported model snapshots.

Available now. Access and delivery agreed for the selected scope.

Architecture viewer

Which question does it answer? Explore bounded contexts, service integrations and architecture dependencies.

For: Architects and engineers reviewing service dependencies.

Use when: Explaining integrations during design review or onboarding.

Bring -> get: Blueprint model -> interactive context and service views.

Architecture viewer showing the context map of the PrestaShop model: twelve bounded contexts in value-stream lanes, with their declared dependencies.Open full-size picture

Blueprint graph viewer

Which question does it answer? Explore entities, relationships and the modeled reach of a change.

For: Engineers exploring modeled relationships.

Use when: Investigating what a proposed change touches.

Bring -> get: Blueprint model and starting entity -> interactive graph and impact views.

Blueprint graph viewer showing the impact of the Submit Order operation in the ecommerce model: the rule, test, story, concept and event it reaches, listed hop by hop.Open full-size picture

PRD Viewer

Which question does it answer? Explore goals, requirements, risks, decisions and delivery plans for a product.

For: Product teams reviewing goals and requirements.

Use when: Discussing measures, supporting work and threats to a goal.

Bring -> get: Blueprint model -> interactive requirements views.

PRD Viewer showing the goal Cart-to-order conversion rate above 3.5%: what it affects, its measure and KPI, what works toward it and the risk and inquiry that threaten it.Open full-size picture

VS Code extensions

Read and edit Blueprint files with model navigation and previews beside your source.

Archally Pro

Archally Preview

Which question does it answer? What architecture does this arch file describe?

For: Architects reviewing architecture while editing a model.

Use when: Reviewing an arch file beside its diagrams.

Bring -> get: Saved arch files -> live context map, domain map and contract surface previews.

How to get it: Archally Pro: a VSIX in a pilot or on request.

Apache-2.0

Blueprint Navigation

Which question does it answer? Where is this Blueprint id defined, and what does it mean?

For: Model authors following references across Blueprint files.

Use when: Reading or editing an id reference.

Bring -> get: Blueprint files -> go-to-definition, hover and id highlighting.

How to get it: Open source under Apache-2.0. VSIX on request until published on the VS Code Marketplace.

Archally Pro

Roadmap Gantt Preview

Which question does it answer? What does this roadmap look like on a timeline?

For: Delivery leads reviewing a roadmap while editing it.

Use when: Saving a roadmap file and checking its timeline.

Bring -> get: Saved roadmap file -> Gantt preview beside the editor.

How to get it: Archally Pro: a VSIX in a pilot or on request.

CLI tools

Separate tools share the bp command package. Each family serves a different modeling task.

Available now. Access and delivery agreed for the selected scope.

Browse the model

Which question does it answer? What entities and relationships does the model contain?

For: Model authors finding entities and relationships.

Use when: Locating recorded knowledge before editing or review.

Bring -> get: Blueprint model and query -> matching entities and relationships.

A terminal running bp query for cart on the PrestaShop model: eight of 258 matches with their type, name and layer.Open full-size picture

Verbs: list, context, model, entities, query, node, neighbors, subgraph, markdown, scope-tree, reload

Impact and paths

Which question does it answer? Which dependencies and paths connect the entities affected by a change?

For: Engineers assessing a proposed change's modeled reach.

Use when: Deciding which dependencies to inspect before a change.

Bring -> get: Blueprint model and starting entity -> modeled dependency impact.

A terminal running bp impact for the CreateCart operation: the twelve entities one hop away, with their type and the relation that reaches each.Open full-size picture

Verbs: impact, aggregate, follow-path, shortest-path, nfr

Model checks

Which question does it answer? Is the model valid and connected, and what has changed?

For: Model reviewers checking validity and changes.

Use when: Before accepting a model revision.

Bring -> get: Blueprint model -> validation, quality and change reports.

A terminal running bp validate on the PrestaShop model: 173 files validated, no schema or cross-reference errors, one gap warning, PASSED.Open full-size picture

Verbs: validate, check, quality, status, diff

Code and infrastructure alignment

Which question does it answer? How does the model align with code, infrastructure, ownership and artifacts?

For: Engineers reviewing model and implementation alignment.

Use when: Checking ownership and coverage evidence before delivery.

Bring -> get: Blueprint model and implementation references -> alignment reports.

A terminal running bp ownership on the PrestaShop model: for each bounded context, how many operations it owns through contracts and through its domain.Open full-size picture

Verbs: coverage-check, reconcile-report, iac-coverage, infra-check, ownership, affects-report, artifact-content

Render

Which question does it answer? How can I generate coordinated diagrams, reports and contracts from a model?

For: Model authors delivering configured artifacts.

Use when: Generating the targets agreed in a project's render manifest.

Bring -> get: Blueprint model and render manifest -> configured artifacts.

A terminal rendering one target of the PrestaShop manifest with its provenance stamp: the run summary, its notes and the delivery gates that passed.Open full-size picture

Verbs: render

Edits

Which question does it answer? How can I preview and make validated changes to model files?

For: Model maintainers preparing structured edits.

Use when: Previewing or applying a model change.

Bring -> get: Blueprint model and proposed edit -> preview or updated model.

A terminal previewing a change to the CreateCart operation's summary with bp propose, nothing written, and bp next-id returning the next free command id.Open full-size picture

Verbs: next-id, propose, new, patch, append, verify, tags, rename, rewrite-refs, move, split-file, merge-file, schema-update

Tracked migrations

Which question does it answer? How can I stage, review and explore planned model changes?

For: Model maintainers tracking model evolution.

Use when: Reviewing staged changes or alternative states.

Bring -> get: Blueprint model and staged changes -> migration records and review.

A terminal on a scratch copy: tracked mode enabled, a migration created, a change staged into it, and the migration review listing the staged change and the entity it affects.Open full-size picture

Verbs: migration, stage, one-shot, variant

Blueprint MCP

20 registered tools let an AI agent read and query Blueprint models, inspect dependencies, check validation and find modeling guidance.

Available now. Access and delivery agreed for the selected scope.

Blueprint MCP

Which question does it answer? Query entities and relationships, trace impact, inspect validation and ownership gaps, and retrieve modeling guidance.

For: Agent developers grounding an AI task in model evidence.

Use when: Giving an agent structured model context.

Bring -> get: Blueprint model and MCP request -> model query results and guidance.

A Blueprint MCP tool call get_neighbors for the CreateCart operation and the start of its result: the context, operation, event and concept it connects to.Open full-size picture

GraphQL server

A shared model API for connected Blueprint viewers.

Available now. Access and delivery agreed for the selected scope.

Blueprint GraphQL server

Which question does it answer? Serves model queries to the architecture, graph and PRD viewers in connected mode; exported snapshots support standalone viewing.

For: Viewer developers connecting model queries to views.

Use when: Supplying a connected viewer with model data.

Bring -> get: Blueprint model and GraphQL query -> structured model results.

A GraphQL impactReport query for the CreateCart operation and the start of its JSON result: twelve reached entities with the relation that reaches each.Open full-size picture

A request starts a scoping conversation. Executables and hosted accounts are supplied only where agreed.

Validator or semantic checker?

The validator checks schema conformance and cross-file references, with gap warnings.

The semantic checker checks relationships for modeling issues beyond schema validity, such as orphan entities, missing causal links and untested rules.

Both report on the model; neither proves the running system correct.

The schema updater previews and applies supported version migrations. It retains source version directories when creating the next version and reports items requiring manual work. Preview first and validate afterward.

Read about schema versions and migrations

Each viewer shows the current state of the model and, within its recorded scope, the state of the system's context. Review that model against code, tests and runtime evidence.

Worked examples from public models

See the question, the exact request and an excerpt of the recorded result.

What order entities and relationships does this model record?

This Blueprint MCP answer reports the order relationships recorded in the ecommerce model.

Request or command

{
  "name": "query_graph",
  "arguments": {
    "project_id": "ecommerce",
    "filters": {
      "text_contains": "order"
    },
    "include_relations": true,
    "limit": 5,
    "max_edges": 8
  }
}

Result excerpt

{
  "entities": [
    {
      "id": "CN003",
      "type": "Concept",
      "name": "Order"
    },
    {
      "id": "CMD002",
      "type": "Operation",
      "name": "Submit Order"
    },
    {
      "id": "CMD003",
      "type": "Operation",
      "name": "Cancel Order"
    },
    {
      "id": "EVT002",
      "type": "Operation",
      "name": "Order Submitted"
    },
    {
      "id": "EVT003",
      "type": "Operation",
      "name": "Order Cancelled"
    }
  ]
}
{
  "source": {
    "id": "CMD002",
    "type": "Operation",
    "name": "Submit Order"
  },
  "type": "produces",
  "target": {
    "id": "EVT002",
    "type": "Operation",
    "name": "Order Submitted"
  }
}

Five entities shown from twelve matches; eight relationships returned, with more omitted.

Inspect the pinned public model

Which modeled entities mention an order?

This bp query locates order-related entities in the public model.

Request or command

bp query ecommerce --text order --limit 5 --json

Result excerpt

{
  "entities": [
    {
      "id": "CN003",
      "type": "Concept",
      "name": "Order"
    },
    {
      "id": "CMD002",
      "type": "Operation",
      "name": "Submit Order"
    },
    {
      "id": "EVT002",
      "type": "Operation",
      "name": "Order Submitted"
    },
    {
      "id": "CMD003",
      "type": "Operation",
      "name": "Cancel Order"
    },
    {
      "id": "EVT003",
      "type": "Operation",
      "name": "Order Cancelled"
    }
  ]
}

Five entities shown from twelve matches.

Inspect the pinned public model

Which bounded contexts depend on each other in the public PrestaShop model?

This Context Map SVG shows bounded contexts and modeled dependencies across the whole public PrestaShop model at one pinned revision.

Request or command

bp render prestashop --generated-at 2026-11-09T12:00:00Z

Result excerpt

12 bounded contexts and 16 modeled dependencies.

Context Map of the public PrestaShop model: bounded contexts and their dependencies
Diagram in English.

Inspect the pinned public model

What these examples establish

Text matching locates modeled order entities in ecommerce. It does not traverse dependencies or establish runtime failure. The PrestaShop render shows modeled bounded contexts and dependencies across the whole model in a Context Map SVG; it does not establish runtime behavior.

Start with one change initiative

We agree the scope and terms of a pilot individually, starting with one change initiative and one bounded context.

Agree the reader questions, source evidence, model, supported views, review responsibilities and handover in the proposal. Tool access, licences and adaptations are part of that agreement.