Approach · Knowledge in an Intended Design
Business knowledge that AI can build on
The Intended Design describes your application from the business side: what it is, what it does, how it looks, how it connects and where its data lives. People and AI agents work on the same Intended Design, the engine checks it as a whole, and it produces ordinary code you can run anywhere.
Six views
One application, described across connected views
Manifesto
The Intended Design comes first
zAppDev lets you build full-stack, agent-ready applications from an Intended Design. You describe the application and program all its logic across every tier in one language, so the whole application can be verified and validated before any code is produced. The engine produces the code for each tier. AI helps you create the Intended Design, and every change to it is checked.
The Intended Design also comes equipped: it is built around established patterns and standards, integrated so they work together. See how.
Connected graph
The Intended Design as one connected graph
Every element is a node. Every relationship is an edge. This is a slice of a real kind of application: a sign-in flow that reaches from intent to the database.
Illustrative slice of the Web application template. Ask the graph what would break if the Role object changed, and it answers across every view.
The whole stack
Checked as one system
A full-stack application usually spans several technologies: a database, a server, a web or mobile client, and the API between them. Each has its own language and tools, so nothing sees the whole application at once, and keeping the tiers consistent is left to the team.
Checked together
The engine reads the whole Intended Design, so it can check the database, the server and the client together. A rule written once in the logic reaches every tier, and a change that would leave one tier out of step is reported by the checks.
Open to agents
MCP opens all of it to AI agents. They can read the Intended Design, change it, validate it and build it, and they work through the engine, not around it.
The AI era
Why this matters now
When AI works on your application, the Intended Design is what is worth protecting. And because every service can become an MCP tool, the applications you build are ready for agents to use. How AI uses it →
Semantic isolation
Each view is described in its own terms. A change to the interface cannot silently rewrite the rules, and the AI works on one view at a time.
Governed at the Intended Design
Reviews, approvals and audits happen on the Intended Design. The generated code stays open for anyone who wants to read it.
Why views
Small questions, one at a time
People do not hold an application in their heads as files. They hold purposes, business concepts, rules and screens, and the links between them. The six views give a tool the same shape, so what people understand and what the tool holds line up.
Chunking
Six views keep each question small.
Association
Links mirror how ideas connect.
See the approach in practice
Open Studio and build a connected application, view by view.
Create free account Read the approach in the docs