An effect class is a label on every tool call an agent makes, saying how hard the action is to undo. In Heighliner there are four:
| Effect class | Example | Who decides |
|---|---|---|
| Pure | Read metrics, run a query | The agent, freely |
| Reversible | Open a pull request, flip a feature flag | The agent, within policy |
| Compensatable | Charge a card (undo is a refund) | Policy, often a person |
| Irreversible | Email customers, delete data | Always a person |
Effect classes decide which actions run on their own and which wait for an approval. Irreversible actions are held in escrow until a person approves. Connectors that cannot safely repeat a call get their effect class raised one level.
Related
- EscrowEffect escrow stages an agent's irreversible actions, like sending email, in an outbox and releases them only after approval and when the run commits.
- Approvals without rubber-stampingAsking a person to approve every agent action turns oversight into clicking yes. Effect classes, escrow and saved rules keep approvals rare and meaningful.
- ProductWhat every Heighliner fleet gets: a dollar budget with a hard stop, schedules and triggers, a sandbox per agent, approvals for risky actions and an audit trail.