Architecture modeling scoped to one change initiative

A scoped InPerceptic service using the Blueprint reference schema or a tailored schema. Agree deliverables per engagement; adapters are priced separately.

Scope the model around your next decision

Blueprint Modeling Engagement is an available InPerceptic architecture service under Archally's Collaborative Intelligence for SDLC. Start with one change initiative; we model one bounded context of it with you.

Use the reference schema where its concepts answer your questions, or scope a tailored schema when they do not. Delivery is agreed per engagement. Adapters and tool adaptations are priced separately.

Use the reference or scope a tailored schema

Reference-schema modeling

Select supported Blueprint concepts, author a representative YAML model and review its source links. Agree which supported views and checks answer the team's questions.

Schema tailoring

Agree the missing concepts and relationships first. Scope a candidate schema or profile, its rationale and a representative model. Confirm the required consumer adaptations before agreeing outputs.

The proposal names the deliverables: a model, schema or profile, rationale, checks, supported team views and handover as applicable. It does not assume a fixed package of every adapter. The Apache-2.0 reference schema licence does not license the whole toolchain.

From discovery call to handover

01

Discovery call

Bring one active change initiative. Identify the readers, questions, representative scenarios and authoritative sources.

02

Scoped proposal

Agree the boundary, deliverables, price, timeline and review responsibilities. Scope any schema tailoring and price adapters separately.

03

Model and review

Work through the selected scenarios together. Review the model against source revisions and check the agreed views. Record discrepancies and decisions.

04

Handover

Agree how your team receives the model, rationale, checks and supported views, and who maintains them. Confirm tool licences and any training in the proposal.

Want to automate your SDLC with AI agents?

A workshop for your team with Adam Walkowski, creator of Archally, at your company or online. Learn how to automate software delivery with context shared in Markdown and Blueprint models: which tools to build, how to build agents and where to run them. It draws on what Adam learned building Archally with AI agents and designing its schemas.

We agree the scope, format and price with you before the workshop.

Free Digital Chaos Tamers workshops

Scope, sources and ownership

Is the schema fixed, a reference, or tailored?

The public Blueprint schema is the reference starting point. InPerceptic offers schema tailoring today as a scoped service when your questions reveal a gap. Current tooling reads YAML. New concepts or notation can need validation, extraction, graph, query or rendering adaptations; adapters are priced separately.

Do we have to model the whole system?

Start with one change initiative and one bounded context. Select the knowledge needed for the agreed questions, and record what is outside the boundary. Expand when another decision justifies it.

Who authors the model, and who reads it?

Named authors and reviewers maintain the YAML and its source links. Other team members can use the agreed rendered views without authoring YAML. AI agents can query a model where the selected tooling exposes that access; access and review responsibilities are part of scoping. The quality of people's and agents' answers still depends on the model's coverage and review.

Can several models refer to the same code?

Yes, models can record different questions about shared code. Give each model an explicit scope and map its references to the relevant repository, path and revision. Shared code or a shared namespace does not establish automatic semantic federation between schemas.

Can one model span repositories?

It can record a system that spans repositories when the source mappings are explicit. Agree which repositories, revisions and owners each reference means, and review those links as code changes. Colocation and identifiers alone do not reconcile the sources.

Does a checked model prove the implementation is correct?

No. Record whether a statement is intended design or observed implementation. Link authoritative code, automated tests and runtime evidence, retain their review dates, and reconcile discrepancies. Model checks cover specified constraints. A missing test link is a traceability gap, not a test result or runtime coverage measure. Examine modeled change impact, then verify the implementation separately. Check each rendered artifact against the accepted model revision. A consistent view does not establish runtime correctness.

What does this add to diagrams and a wiki?

Typed relationships can connect a rule to its operation, rationale and evidence, then be reused in different views and queries. Keep explanatory prose and workshop diagrams where they help. Review the model and rendered views alongside the sources; no documentation format maintains itself.

We agree pilot scope and terms individually. Tool access, licences, adaptations and handover are agreed in the proposal.

Bring one active change initiative

Agree a bounded pilot with InPerceptic, its source evidence and the views your team needs to make the decision.