Part 3 · Operate
Costs and limits
What each task costs, where the caps are, and what happens when you hit one.
01What it is
Every model call is logged with its task, tier and cost. Caps are enforced server-side and refuse rather than degrade.
02Why it exists
Cost control lives at the model layer rather than in each feature, so a new feature cannot accidentally run an expensive tier. Cheap for classification, strong for judgement and drafting.
Caps refuse with a message rather than silently producing less. A cap that degrades quality without saying so is worse than one that stops.
03How to use it
- 01Watch the actions counter in Settings.
- 02Read the message when you hit a cap. Drafts keep queuing and go out when the period resets.
- 03Check the admin screen for cost per task if you are the owner.
04What good looks like
- You give it
- A month using 140 of 150 actions.
- You get
- Everything sends and the counter shows what is left.
- Why
- The cap is checked before each send and the counter is the same number the gate reads.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- Hitting the free tier and expecting sends.
- You get
- Drafts queue and nothing sends, with the reason stated.
- Why
- The free tier has no outreach actions. Free covers the thinking.
Derived from the rules in the code