-
1. Start with one business question
Choose one business question, its owner and its source. Write a small answer the owner can review: that is your first model.
An example from the public PrestaShop model:
- Question
- May this cart become an order?
- Selected condition
- The cart is not empty, and every line has a quantity above zero.
- Source and reviewer
- The public order rule, reviewed by the product rule owner.
- Still open
- Should a request to buy later also become an order?
Keep other domains out of this first part of the model. A small model is easier to check, review and extend.
-
2. Get the public repository
Use your own agent in Claude Code, Codex or Cursor to build a model of your system with Archally. The public repository supplies the Blueprint schema, local checking tools, a modeling agent, commands and method skills. Together they help you capture a shared vocabulary, flows, rules and decisions in YAML that you and your agent can read and refine. You can also write the model by hand and validate it locally. Archally Pro renderers run locally on an offline licence under separate commercial terms.
The kit includes the blueprint-modeler agent, blueprint-new and blueprint-check-all commands, and ddd-modeling, event-storming-modeler and capability-mapping skills.
- The Quick Start in the README
- The AI agent kit guide for Claude Code, Codex and Cursor
- The worked examples
Read the README and the guides from the same revision as your model.
Open the public Blueprint repository -
3. Work with your agent in the console
A shell block holds commands for your terminal. A request block holds an instruction you type into your agent. Each has a copy button.
Prepare the repository
With Node 22 or later, clone the repository and build its local tools. These are preparation steps, not an installer.
git clone https://github.com/Archally/blueprint-schema.gitcd blueprint-schemanpm installnpm run buildCopied. Copying did not work. The text is selected: copy it with your keyboard.
Open the folder in your agent
- Claude Code: open a terminal in the repository folder and run
claude. - Codex: open a terminal in the repository folder, run
codexand trust the folder, so the blueprint-modeler agent loads. - Cursor: open the repository folder itself as the workspace with File, Open Folder.
Each host reads the kit only from the folder you open, so open the repository folder itself.
Ask for one bounded change
Give the agent one question, its scope, its sources and the schema. Ask it to separate observations from inferences and to name what stays open.
Read the rule orders.SR001 and the command orders.CMD001 in examples/prestashop/.blueprint/v2.8/orders/.Using the selected cart rule and its command link, draft a short explanation of when this condition is met. Cite the rule, separate observations from inferences, and flag whether it settles the empty-cart request.Copied. Copying did not work. The text is selected: copy it with your keyboard.
This is an illustrative request, not a recorded agent session.
Review the proposed change
A valid YAML change can still overstate the rule. In this invented example the agent proposes:
summary: "A non-empty cart always places an order."The reviewer rejects “always”: the rule also requires quantities above zero, and other conditions stay open. The corrected summary reads:
summary: "Selected condition: non-empty cart and positive line quantities."The product rule owner still decides whether an empty cart may become an order.
Run the checks and review the result
Ask the agent to run the kit's checks:
Run /blueprint-check-all examples/prestashop/.blueprint/v2.8Copied. Copying did not work. The text is selected: copy it with your keyboard.
In Claude Code and Cursor you can also type the command after a slash. In Codex, ask as written, so it follows the command file. Approve the three npm run commands when your agent asks, then read the findings with the rule owner.
When agents work in several steps
- Give each agent one bounded change, ready to start, with the criteria for accepting it.
- Assign work to a role only when it has the authority and the tools the work needs.
- A passing model check is not evidence that the system behaves as described.
- Only the owner's actual answer settles an owner decision.
- A successor resumes from verified state, and work is accepted against its evidence, not against a claim that it is done.
- Claude Code: open a terminal in the repository folder and run
-
4. Check and report with the public tools
From the prepared repository root, you can run the checks and the report yourself:
npm run validate -- examples/prestashop/.blueprint/v2.8 --schemas schemanpm run check -- examples/prestashop/.blueprint/v2.8npm run quality -- examples/prestashop/.blueprint/v2.8npm run render -- examples/prestashop/.blueprint/v2.8 -o prestashop-report.md -t PrestaShopCopied. Copying did not work. The text is selected: copy it with your keyboard.
- Validation checks schema conformance and references.
- The semantic checker reports structural findings, and the quality gate reports missing or weak descriptions.
- The public Blueprint renderer produces a Markdown report with embedded Mermaid diagrams. Other tools can also read the YAML model.
Checks do not decide business truth. An exit code of 0 does not mean the model is complete or correct: read the findings and review the meaning with the people who own it.
The schema, examples, documentation, reference validator and agent kit are Apache-2.0. The model builder, semantic checker, quality gate and renderer are FSL-1.1-ALv2. See the licence map in the repository.
-
5. See more with Archally Pro
Pro is optional. Choose a tool after the reader question, then confirm its supported scope and access for your model.
Richer views of the same model
Choose a visualization for the question you need to answer. Pro offers diagram and report renderers and interactive viewers of the same model.
Pro renderers run locally on an offline licence under separate commercial terms. Ask for access.
Explore Pro visualization toolsModel context for your agents
Make the model part of Spec Driven Development (SDD) and your software development lifecycle (SDLC) with AI.
Pro includes Blueprint MCP and the bp CLI. GraphQL is part of the viewer backend.
An agent can query structured model context through Blueprint MCP. That does not guarantee an accurate answer or prove that an effect the model does not describe is absent.
Tell us which question your team needs to answer, and we will confirm what Pro supports for your model.
Ask about Archally Pro access
Would you rather have InPerceptic assess your system with you? Read about the pilot