ASTRA / Approval gate
The approval gate
An approval gate is a hard stop between a drafted action and a real write. ASTRA puts one in front of everything customer-facing and everything that touches a system of record, so an agent can draft freely but cannot commit anything consequential without a person saying yes.
Most AI tooling in go-to-market either observes and reports, or acts on its own and asks you to trust it. The gate is the third option, and it is the reason an agent can be pointed at revenue systems at all.
What exactly is gated?
Always gated
Mail and messages to a customer. Opportunity and deal stage changes. Renewal and close dates. Anything a customer will read or that finance will later report on.
Can run unattended
Reversible internal writes: activity capture, internal notes, hygiene sweeps, an alert to your own Slack channel. Each still leaves a receipt.
Never automated
Anything the customer has not scoped. An agent has no standing authority to invent new categories of action for itself.
Why not just trust a good model?
Because the failure mode is asymmetric. A model that drafts a slightly wrong internal note costs a few seconds. A model that emails the wrong pricing to a customer, or silently moves a close date that a board deck is built on, costs something you cannot take back with a retry.
Model quality reduces how often the bad case happens. It does not change what happens when it does. A gate does, which is why the gate is structural here rather than a toggle in a settings page.
Does approving everything not just move the work?
It would, if approving were as expensive as doing. It is not. Reviewing a drafted action is reading one screen and deciding yes, edit, or no. Producing that same action by hand is opening four tools and retyping what you remember.
The design target is a rep clearing the day's drafted actions in about ninety seconds, in one place, rather than context-switching for the rest of the afternoon.
What does the reviewer actually see?
The action, the systems it will touch, and the moment in the call it came from, quoted. That last part matters more than it sounds. An approval you cannot trace back to something the customer said is a guess with extra steps.
Illustrative, not a customer record.
What happens to a rejected action?
Nothing is written, and the rejection is recorded alongside the draft. That record is useful: a pattern of rejections on one workflow is the clearest signal that the workflow is wrong, and it is the input to the next iteration.
Rejections are not failures of the system. They are the system working.
Questions
What is an approval gate?
A hard stop between a drafted action and a real write. The action is fully prepared but cannot execute until a person approves it. In ASTRA everything customer-facing and everything touching a system of record is gated.
Can we turn the approval gate off?
Customer-facing and system-of-record writes stay gated. Reversible internal writes can be allowed to run unattended, and those still produce a receipt that can be rolled back.
How long does reviewing take?
The design target is a rep clearing the day's drafted actions in about ninety seconds, because reviewing a prepared action is far cheaper than assembling it by hand across four tools.