Blueprints on the new engine.
Everything Archie writes now comes from its new reasoning engine: conversations since September, plans and blueprints since October 5. Plan summaries keep up with their blueprints, the console is about four times faster, and Catio reads your code with sharper eyes.
What this means for you
Big plans finish.
Ask for a wide architecture plan and the new engine keeps working until it is done. No more coming back to a run that gave up at blueprint three. The summary and figures stay in step with the blueprints, so the big call rests on what the plan says today.
A console that keeps up.
A typical page shows its main content in under a second, down from over three, and clicks and typing answer in about 16 ms. It works on a phone, so the plan review can happen in the taxi, if that is how you live.
A sharper model of what runs.
Catio now tells a service from a worker, a batch job, a scheduled job or a command-line tool, across more languages and frameworks, and links each one to the infrastructure it really runs on. A worker filed as a service is a small mistake that becomes a wrong recommendation two steps later. Fewer of those.
- Plans and blueprints run on Archie's new engine. Every customer, nothing to turn on, since October 5.
- A plan's summary and figures follow its blueprints within a couple of minutes, on their own.
- The console is about four times faster at a typical page load, and works on phones.
- Catio reads your code more sharply: more languages, five kinds of workload, correct links to infrastructure.
Blueprint generation, on the new engine
Ask Archie for a plan or blueprints and the new reasoning engine writes them, the one behind every Archie conversation since September. It keeps working on a large request until it is done. Every customer with Blueprints has it, nothing to turn on, since October 5.
The September post promised this as phase two. Same grounding, same checks, same habit of showing its work, now applied to a whole program of blueprints. Older blueprints are untouched and keep their history. Nothing was reorganized while you slept.
Read more: Docs: Blueprints
Plans that stay current
A completed plan's summary and figures are written from the blueprints inside it. Add or remove a blueprint, edit a section, change a setting that moves the figures, or regenerate a blueprint, and the summary card says Pending update, then Refreshing, then Up to date, within a couple of minutes. Nothing to click.
A summary that drifts from its blueprints is how a program gets approved on numbers nobody re-checked. Now the page tells you when it is catching up, and when it has caught up.
A console rebuilt for speed and every screen
A typical page now shows its main content in under a second, where it took over three. The server answers in about 150 ms and clicks and typing respond in about 16 ms. It works on phones and narrow windows: tables wrap, buttons fold to icons, and dialogs no longer summon the keyboard uninvited. Buttons, colors, inputs and dates match across the product. Under Account, Appearance, pick a light, dark or system theme, larger text and reduced motion.
A faster console makes every other feature better for free. The figures come from real production page loads in mid October, at the 75th percentile. The samples are small. Every measure moved the same way.
Sharper understanding of your code
Catio reads your repositories to learn what runs, now across more languages and frameworks. It tells a service from a background worker, a batch job, a scheduled job and a command-line tool, gives each its own icon in Stacks, and links it to the infrastructure it runs on more reliably than before. Live since October 15; a workspace with source code connected gets it on its next run.
The living model is only as good as its reading of your code. A job linked to the wrong cluster looks harmless right up until a recommendation is built on it.
Read more: Docs: Stacks
What we measured
Phase three
- Archie in your coding assistant, over MCP. It already runs on the new engine; the public release is next.
- The public API, with API keys you manage in Settings.
- On-premises estates through Device42, and Azure.
- Signed-off and Locked states on blueprints, so a ratified record stays ratified.
- Archie learning from its own run history, with a person approving what changes.
Elsewhere in the console this month
- Oct 16Blueprint UI revisions.
- Oct 16Generate designs from recommendations to get a more detailed plan.
- Oct 16Copy a link to an Archie chat.
- Oct 16The organization and workspace you are in show in the top bar; the console returns you to your last organization.
- Oct 16Workspaces are listed in name order, and tenants with more than fifty see all of them.
- Oct 16Delete invitations; suspend or activate a user from their row.
- Oct 16Scroll bars show on pages, panels, lists and blueprint pages.
- Oct 16A failed read shows an error message.
- Oct 16Archie's home chat recovers after the tab was hidden, and no longer jumps to the bottom while you read.
- Oct 16Account, Appearance: light, dark or system theme, larger text, reduced motion.
- Oct 15Integration Run now shows as running at once on every page.
- Oct 13Large Stacks views open with less waiting.
- Oct 09The console works on phones and narrow windows.
- Oct 06Workspaces, integrations and subscriptions pages page through results; integrations get Subscribe to all and a subscription count.
- Oct 06A plan whose run has stopped is marked failed within a day.
- Oct 06Bug fixes, including blueprint counts and pagination.
Want to see it on your own system? Book a demo