Blueprints, from draft to decision.
A review path on every blueprint, the summary up top, every version kept, and a chat that knows which blueprint you mean.
What this means for you
A decision is recorded, not implied.
Every blueprint has a status, and the decision that moves it on is explicit: accepted or declined. A plan shows how many of its blueprints have made it through, so a program's progress is visible without a spreadsheet, and the big call rests on designs that were actually decided.
You know which blueprints are committed authorities.
An Accepted blueprint carries the team's decision, and Completed marks the end of the path. That is the standard what ships is measured against, and it lets architects govern by exception instead of gatekeeping. Blueprints that were generated and used but never reviewed are visible too, which is exactly where exception-based scrutiny should look.
Version history is decision history.
Every version of a blueprint is kept, with who changed it and, for Archie's edits, the reasoning behind the change, so an architect can later see how a design reached the shape it did. Comments, reactions and decisions are recorded when they happen. That record is the memory the next blueprint starts from; Archie learning from it is next.
- A review path on every blueprint, run like an architecture review board: Draft, accept or decline, In Review, Completed, with the decision kept on the blueprint.
- Every newly generated blueprint opens with an executive summary, written after the rest so it reflects all of it.
- Mention a blueprint or a view by name in an Archie chat, ask about the page you are on, and bring your documents into the conversation.
- Version history on every blueprint, with who changed it; edits made with Archie persist and carry their reasoning.
- Plans link to the files they were generated from and show their progress; several blueprints can be added to a plan at once.
From draft to decision
A blueprint now moves through a review path: Draft, then a decision to accept or decline it, then In Review, then Completed. A blueprint that has been overtaken can be marked Superseded or Canceled. The decision lives on the blueprint itself, where the next reader will find it. Plans show how far along they are, and several blueprints can be selected at once to add to a plan or to delete.
You told us design decisions needed a lifecycle: draft, under review, approved or rejected. This is that path, and it maps one-for-one to what an architecture review board expects: a proposal, a review, a decision, delivery, and supersession. It is the shipped half of architecture decision records; the ratification freeze, Signed-off and Locked, is next, so a ratified record cannot drift after sign-off.
- Draft
- Generated or authored; not yet decided on. Usable at AI speed without review.
- Accepted / Declined
- The team's commit decision: this is the design to pursue, or not.
- In Review
- Under active review after acceptance.
- Completed
- The end of the review path.
- Superseded / Canceled
- Overtaken by a newer blueprint, or dropped.
- Signed-off / Locked (next)
- The ratification freeze: a ratified record that cannot be edited afterward.
Read more: Docs: Blueprints
Mention it by name and ask
Type @ to mention a blueprint or a Stacks view by name and ask about it. A document attached to the chat is read alongside the living model, as before. Archie also knows which page you are looking at, so a question asked from a blueprint is about that blueprint. Edits made with Archie persist, and every blueprint keeps its version history: each version with who changed it and, for Archie's edits, the reasoning behind the change.
Attaching a requirements document is the fastest way to a design that respects it, and mentioning a blueprint by name is how a follow-up question stays on the thing you meant. Together they replace pasting paragraphs into a prompt. And because every version is kept with who changed it, a blueprint's history reads as the decisions that shaped it.
Read more: Docs: Who is Archie?
The summary comes first
Every newly generated blueprint now opens with an executive summary: the headline in the first sentence, roughly 150 to 250 words, and it reflects the whole blueprint rather than a first guess. The PDF export carries the summary, the diagram with its legend, and the sections.
You told us twenty-page responses are not consumable. The summary is the first step; a one-page review pack for architecture boards, with a technical view and an exception register, is the next.
How it works, in one lineThe summary is written after all the other sections are complete, and its figures are checked against the blueprint's own numbers.
What we measured, and what we did not
From decision to sign-off
- Signed-off and Locked states, with an approval record, so a ratified blueprint cannot change after sign-off.
- A one-page review pack for architecture boards: summary, technical view, exception register.
- A review view that compares what shipped with the committed blueprints and shows only the exceptions.
- Standards pulled straight from a SharePoint folder.
Elsewhere in the console this month
- Sep 25Executive summary on every newly generated blueprint; the PDF export carries the diagram and legend.
- Sep 25Review path: Draft, Accepted or Declined, In Review, Completed, Superseded, Canceled.
- Sep 24Blueprint diagrams read relationship subtypes from the component library and label grouped edges.
- Sep 23Blueprints: multi-select with bulk delete and add-to-plan, plus a Creator column.
- Sep 21Archie knows which page you are on; tool steps are labeled in plain words; the Sources list pages.
- Sep 09Mention a blueprint or a Stacks view by name with @ in an Archie chat.
- Sep 08Plans link to the source files they were generated from.
- Sep 04Version history on every blueprint.
- Sep 03Edits made with Archie persist, and Archie's revisions carry their reasoning.
- Sep 02Blueprint export to PDF.
Want to see it on your own system? Book a demo