
How the guardrails are enforced
Where the limit actually lives, why it is checked at the action rather than reconciled overnight, and what an agent sees when it hits one.
Notes on building the workspace between agents and the people who answer for them.
Six placeholder entries, here to show the layout. The first is written, the other five are not. Covers are generated from the site stylesheet, so they cannot drift from it.

Where the limit actually lives, why it is checked at the action rather than reconciled overnight, and what an agent sees when it hits one.

The real bill for one sender across a month: infrastructure, the model, and the hours a person still spends in the inbox.

A reply is where the deal is carried forward or lost. The argument for keeping that decision with a person, and for making it cheap.

One shared workspace token makes every action anonymous. What changes when each integration carries its own key.

Why a sequence posted over the API arrives in a draft state, and why launching it is a separate call.

The warm-up ramp, in practice: what to send, how much, and the mistakes that cost people an account.