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.
Reference and delivery status
Read status notes →- Available reference schema, Apache-2.0
- Reference version checked against the Blueprint monorepo
- Schema version does not establish Designer, Studio or Pro release status
- Agree tools, supported formats and deliverables with InPerceptic; adapters priced separately
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.
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.
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.
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 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.
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.
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.
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.
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.
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.