What is Taiga?

Taiga turns conversations into structured, policy-compliant specifications, and then plans and builds the work that follows from them.

You describe what you want in a conversation. Taiga produces a specification from it, derives the supporting documents (user flows, architecture, data flow, security and privacy assessments), slices the result into initiatives, and its agents implement them against your repository.

Two ways in

That is the path for something new. A product can also start from a repository you already have.

An import reads the repository instead of asking you to describe it, and drafts the product’s documents from what is actually there rather than from what you intended. Nothing asks you to describe the system, because the code has already answered the question. Everything after that, the initiatives and the agents that build them, is the same product either way.

What the agents can build against is a finite list, and languages and frameworks is that list.

Policy-aware, and what that means

“Policy-compliant” is not a slogan here. Your organization records the industries you operate in, your languages and frameworks, and your clouds. Taiga builds a set of policies and an approved tech stack from those answers, and every industry you select adds its own regulatory controls.

Everything downstream is shaped by them: the specification, the architecture, the security assessment, and the plans the agents work from. This is why setting up the organization comes before creating a product.

Three loops

A product in Taiga is organized as three continuous loops rather than a sequence of phases. They run in parallel, at different speeds, and feed each other.

Loop	The question it answers	What lives there
Learn	Are we building the right thing?	Discovery, and the product’s documents
Deliver	Can we turn intent into production?	Initiatives, agent runs, deployments
Operate	Is it working in the real world?	Maintenance sweeps, monitoring

The loops are how Taiga thinks about a product, not a menu you navigate. They are the vocabulary this documentation is organized by, so the names are worth knowing before you go further.

Who it is for

• People defining work. Product managers and delivery leads who write the specification and decide what gets built.
• Administrators. Whoever configures the organization: policies, factories, access, and connections to your source control and clouds.
• Engineers. Anyone reviewing what the agents planned and produced, or working alongside them in the same repository.

You do not need to be technical to use Discovery, and you do not need to have used Taiga before to review what it produced.

Where to go next

• Set up your organization if you are the first person here.
• Your first product if the organization already exists.
• Organizations, factories and products for how the three levels relate.