Frequently asked questions

AI Transform Studio is an AI agent harness for enterprise transformation and enterprise architecture work. It connects your strategy, architecture, delivery, and knowledge sources, then lets a person and an agent work the same problem on one canvas. The work ends in a living artifact the team can reopen and refresh.

It depends on the question you bring. If you need to answer impact, sequencing or dependency questions across live architecture, delivery and service systems, and leave the forum with an artifact it can reopen, Studio fits: the agent does the reconciliation under your control. If you need a system of record for your architecture, keep your EA repository; Studio sits above it and does not replace it. If a one-turn chat answer is enough, a general assistant is cheaper.

An agent harness is the controlled loop around a model that lets an agent do long, real work. Ours is built for one domain, enterprise transformation. The agent plans the approach, keeps a goal for long work, uses tools, waits for approval before it writes, and keeps a session you can reopen and steer. The model supplies the reasoning. The harness supplies the structure that lets the work run for hours under your control.

Agentic enterprise transformation is transformation work that agents carry out with people, not beside them. Questions such as retirement impact, sequencing risk, and dependency exposure take days of reconciliation across architecture, delivery, and service tools. Here an agent does that work inside a harness, against your connected sources, while the people involved steer the analysis and make the decision.

Agentic enterprise architecture is enterprise architecture work where agents retrieve, trace, draft, and revise alongside the architect. The architect keeps the judgement. The agent reads the connected sources and builds views such as boards and roadmaps on the canvas. The result is a current picture of the estate that leadership can reopen, not a deck that is out of date by the next forum.

AI enterprise architecture can mean two things: designing the enterprise's own agents, models, and integrations, or using AI to do enterprise architecture work. Studio is built for the second. It also gives teams building with AI a controlled place to run agents: their own models, their own connected tools, and approval before any write.

Studio is organised in layers. Models and integrations are inputs: models supply reasoning and integrations supply reach. The harness is the foundation, the loop that plans, uses tools, and gates writes. Agents and skills sit on top as capacity. The Stage is where the work lands, as artifacts you can reopen.

It is for enterprise architects and heads of enterprise architecture, transformation and PMO leads, and corporate AI builders. Architects use it to answer impact questions and leave leadership a picture they can reopen. Transformation leads use it to give business and IT one artifact for the steering forum. AI builders use it as a controlled place to run agents on their own models and connections.

You bring your own. Your organization connects the model providers it already trusts, tests each connection, and enables the models its members can use. Inference stays on the routes and accounts you control.

Studio Judge runs on the decision model your organization connects, and the decision models it supports today have no EU processing route. When it judges records, the fields it needs from each record are sent to that model. An organization that needs EU-only processing can leave Judge unconnected; assessments and judge stages need it.

Each organization is its own tenant boundary. Members, models, connections, and artifacts live inside it. The product guide is public, and your organization's work stays behind sign-in.