Archally Features & Capabilities

Model selected system knowledge, render views for team questions, and review proposed change. Keep code, tests and runtime evidence linked and reviewed separately.

Read the Blueprint v2.8 reference schema. Reference version checked against the Blueprint monorepo on 2 November 2026. Tool availability and engagement deliverables are scoped separately.

v2.8 Reference Schema Version checked on 2026-11-02
Apache-2.0 Schema Licence The reference schema; tool licences are separate
YAML Model Format Typed concepts, relationships and constraints
Views and contracts Rendered Artifacts Supported mappings and output checks are scoped per tool

Reference and delivery status

Read status notes →
Blueprint reference schema v2.8 Checked 2026-11-02
  • Available reference schema, Apache-2.0
  • Reference version checked against the Blueprint monorepo
Tool and service scope Confirmed during engagement scoping
  • Schema version does not establish Designer, Studio or Pro release status
  • Agree tools, supported formats and deliverables with InPerceptic; adapters priced separately
Model

Record the knowledge needed for a decision

Blueprint is the architecture modeling approach and tool family. A schema defines the concepts, fields, relationships and constraints; a model is an instance recording selected knowledge about your system. A view presents that model for a reader's question.

Architecture viewer Context Map of the public PrestaShop model: twelve bounded contexts such as Checkout, Orders, Catalog and Customers in value-stream lanes, marked core, support or generic, joined by dependency lines.
Architecture viewer. Public PrestaShop model v2.8, as-is: the twelve bounded contexts it records, in value-stream lanes, and the dependencies declared between them. A declared dependency is a modeled statement, not an observed call. Open the picture to read it at full size.
Architecture viewer Context Map of the public PrestaShop model up close around the Orders bounded context: Checkout, Orders, Shipping, International, ExternalApiConsumers and Modules each open to their full card with owner, strategic classification, inbound commands and queries, services, language and questions, while Catalog and Admin are cut by the right edge and dependency lines run between them.
Architecture viewer. The same map up close around Orders: at this zoom each bounded context opens to show its owner, the commands and queries that come in, its services and its terms. Open the picture to read it at full size.

Typed concepts and relationships

Use YAML to connect bounded contexts, operations, rules, decisions and stories. Record source revisions and review dates alongside links to implementation evidence.

Reference or tailored schema

Start with the public reference schema. Scope a tailored schema with InPerceptic when your questions reveal missing concepts. New concepts can require validation, graph, query and rendering adaptations; adapters are priced separately.

Visualize

Choose a view for the team's question

Explore selected entities and their modeled relationships in the Blueprint Viewer. Event Storming boards offer Big Picture, Process and Software Design perspectives for discussions around the same model.

Blueprint graph viewer. Public ecommerce model v2.6, as-is: Impact from Submit Order shows the rules, tests, stories, concepts and events the model relates to it, hop by hop. Modeled impact does not establish a runtime failure. Enlarge the film to watch it at full size.

Impact view around Submit Order in the public ecommerce model: the user story, process, test case, actor, event, rule and concept it relates to, with the list of reached entities beside the graph.
Blueprint graph viewer. Public ecommerce model v2.6, as-is: Impact from Submit Order shows the rules, tests, stories, concepts and events the model relates to it, hop by hop. Modeled impact does not establish a runtime failure. Open the picture to read it at full size.

Focused perspectives

Navigate and filter the model by scope and layer. Use a published example to inspect a supported view; tool access and delivery are agreed during scoping.

Check the representation

A view is rendered from an accepted model revision. Check its scope and source review date, then review discrepancies with code, tests and runtime evidence separately.

Render

Render supported diagrams, contracts and reports

Supported projections include Event Storming boards, sequence diagrams, OpenAPI and AsyncAPI contracts, and model reports. Each mapping requires the relevant source data and an output check.

PrestaShop Place order sequence across modeled participant lanes.
Place order sequence. The Place order sequence shows messages across modeled participants. It describes the model rather than a captured runtime trace. Static preview of the sample shop model.

Contracts with explicit bindings

OpenAPI and AsyncAPI outputs use modeled operations, payloads and exchange bindings. See the projection page for supported delivery paths and the limits of each output.

Reports with a boundary

Model reports can show specified behavior and test links. Those links do not report test execution or runtime coverage. Re-render and check outputs after the accepted model changes.

Evolve

Review modeled change alongside implementation evidence

Record proposed changes and rationale as structured migrations. Compare supported modeled states and keep the YAML in Git for review. Source reconciliation remains an ongoing responsibility.

Test-case coverage report for PrestaShop orders, showing which operations, rules and processes have a test case.
Test cases. Specified behavior and linked test cases provide a review surface during change. This report is not a test-run result or a migration diff. Static preview of the sample shop model.

Intent and observed implementation

State whether a claim describes a design decision or observed behavior. Record disagreements, owners and source dates instead of treating model consistency as real-world correctness.

Shared context for people and agents

Where the selected tools expose MCP access, agents can query model entities and relationships. Agree access, delivery and review responsibilities for your engagement.

Requirements

Trace a requirement to the goal it serves

PRD Viewer reads the goals a model records with their measures, what works toward each goal and which risks threaten it. A missing link stays visible as a gap.

PRD Viewer. Public PrestaShop model v2.8, as-is: the goal Cart-to-order conversion rate above 3.5% with its KPI, the capability, value stream and leverage point working toward it, and the flash-sale latency risk that threatens it. Enlarge the film to watch it at full size.

PRD Viewer Goals Dashboard for the public PrestaShop model with the cart-to-order conversion goal expanded: what it affects, its measure and KPI, what works toward it, and the risk and inquiry that threaten or question it.
PRD Viewer. Public PrestaShop model v2.8, as-is: the goal Cart-to-order conversion rate above 3.5% with its KPI, the capability, value stream and leverage point working toward it, and the flash-sale latency risk that threatens it. Open the picture to read it at full size.

Sources: Blueprint reference schema, public ecommerce reference example, and supported projection delivery paths. Example model and application versions can differ from the reference schema.

See these capabilities in action

Explore the example models, or scope a Blueprint pilot with InPerceptic. Deliverables are agreed per engagement; adapters are priced separately.