From a team question to a reviewed model

Choose the question, model selected knowledge, review its sources, then render and check supported views.

What must your team understand before this change?

Choose one change initiative and the decisions it raises. Which teams and contracts are involved? Which rule explains a constraint? What is intended, and what does the implementation show?

Model the knowledge needed to answer those questions. Link it to code, tests and other authoritative sources, with their revisions and review dates. Review disagreements rather than treating the model as proof.

Questions, a reviewed model, then useful views

01

Choose the representations

Agree the readers and their questions. A context map can show boundaries; a sequence can show message order. Select the relevant concepts and relationships before drawing.

02

Choose or tailor the schema

The schema defines concepts, fields, relationships and constraints. Start with the public Blueprint reference schema, or scope a tailored schema with InPerceptic. Current Blueprint inputs are YAML. New concepts can require validation, graph, query and rendering adapters.

03

Review the model

A model is an instance of that schema: selected knowledge about a particular system. Check its structure, references and specified semantic rules. Review its claims with the people and implementation sources that can substantiate them.

04

Render, check and evolve

Render a supported view for the reader's question. Check it against the accepted model revision. Re-render after model changes, and reconcile the model with changing code, tests and intent. Views do not update external sources for you.

Domain-Driven Design is Blueprint's reference perspective: bounded contexts, operations, rules and decisions give teams a shared vocabulary. It is a starting point for this architecture service, rather than a requirement for every domain or every schema.

Why was order submission designed as asynchronous?

This answer comes from the current ecommerce sample model, reviewed on 2 November 2026. It describes recorded design intent, not a measured performance result.

  1. Question and scope: the Orders model, specifically the rationale for orders.CMD001 - Submit Order.
  2. Recorded decision: orders.DC001 - Use async command for order submission - chooses an asynchronous command to avoid blocking the user while payment and inventory checks complete.
  3. Linked goal: orders.GL001 - Process orders within 2 seconds - is the motivation recorded on the decision. This is a goal, not a benchmark.
  4. Answer and limit: the decision records responsiveness and independent scaling as its rationale, with eventual consistency as a tradeoff. orders.FN001 - A draft-then-submit stage survives in three operations and a lifecycle that no longer has it - records a discrepancy: the running shop has no submit route. The design still needs reconciliation.

Read the smaller public ecommerce reference example (v2.6). The answer above uses the current v2.8 sample; these versions are different. Sources: the Orders decision record, motivation, command definition and implementation finding. The public example may advance separately.

The supported entity lookup returns the decision's rationale and typed links to its goal and command. The list above is an editorial summary of those lookups, not an interactive demo or evidence that the shop implements the decision.

Keep the question and the evidence connected

Diagrams help a team discuss a system; prose preserves context. Typed relationships add reusable links between decisions, rules, operations and sources. A rendered view can reuse those links for another reader question without replacing workshops, code review or operational checks.

Missing requirement-to-test links identify missing traceability. They do not tell you whether tests pass or how much runtime behavior is covered. Schema and reference checks detect specified issues; they do not certify real-world truth.

Read the FAQ on selective modeling, source authority and schema tailoring, or explore supported Blueprint capabilities.

Bring one change initiative

With InPerceptic, model one bounded context of it together. Agree the questions, deliverables and handover; adapters are priced separately.