Tickets & approvals
A ticket is how Typillar makes work concrete before anything is built. The product-manager agent writes tickets; you approve them. This pairing — propose, then approve — is what keeps an autonomous system under your control.
What a ticket is
Section titled “What a ticket is”A ticket turns a plain-language idea into something specific enough to act on:
- a clear scope — what will and won’t be done,
- a name — so it’s easy to find in your project history,
- a short rationale — why this is the right next step.
You’re never approving a vague instruction. You’re approving a defined unit of work.
The approval gate
Section titled “The approval gate”Approval is a hard gate in the build loop:
- Before approval: no code is generated, no resource is created, nothing is deployed. Agents can propose as much as they like; proposing is free and safe.
- After approval: builder agents implement exactly the approved ticket and ship it.
Because the gate sits between proposing and doing, you can leave the PM agent running continuously without it ever running ahead of you.
Your options on a proposal
Section titled “Your options on a proposal”- Approve — the builders implement it and ship.
- Decline / refine — if a ticket isn’t right, adjust your idea and let the agent re-propose. Nothing is built from a ticket you didn’t approve.
Why this protects you
Section titled “Why this protects you”Three things you care about all live at the approval gate:
| You control… | Because… |
|---|---|
| Cost | inference and builds only run on approved work. |
| Direction | only the tickets you accept become part of the product. |
| Timing | nothing ships until you say so. |
Related
Section titled “Related”- Agents & the control plane — who writes tickets.
- Deploys & rollback — what happens after approval.