Skip to content

Glossary

A short reference for the terms that come up throughout these docs.

An autonomous worker in Typillar’s control plane. The product-manager agent proposes work; builder agents implement approved work. See Agents & the control plane.

The point in the build loop where your approval is required before any code is generated or deployed. Agents propose freely; they only act on what you approve.

The repeating sequence at the heart of Typillar: idea → ticket → approve → build → ship. See The build loop.

The part Typillar owns and runs: the agents and the orchestration that drive the loop. It coordinates work but does not host your product or store your data. See Architecture.

A live release of your product to your Cloudflare account, published at a real URL and recorded in your project history. Every deployment is reversible. See Deploys & rollback.

The model work — reasoning and code generation — that powers the agents. It runs on your side (Cloudflare Workers AI or your own key), never on Typillar’s servers. See Zero inference on our servers.

The deliberate division of responsibility: you own the account, repo, data, and inference; Typillar owns the agents and the control plane. See What you own.

A product you’re building, together with its repository, its Cloudflare resources, and its full history. See Your first project.

A concrete, scoped, named unit of work the product-manager agent proposes from your plain-language idea. You approve a ticket before it’s built. See Tickets & approvals.

Cloudflare’s hosted-model service, billed through your Cloudflare account — one of the two ways to run inference on your side.