Every action leaves a record.
Each action is logged with who proposed it, their reason, the rules’ decision, who approved it and the result. Changes people make are logged too.
Every action, with who decided it.
Who proposed each action, which rules ran, who decided, and what happened.
One decision, start to finish
The October 21 budget move, as its history records it. Code records each step as it happens.
- ProposedBy the New Customers agent, with its reason: roast-date messages beat the control by $8 per first order.
- Checked“2 checks passed · reallocation needs approval.” The total stayed at $212, so the 20% limit passed, but one campaign moved 97%, over the 50% that needs a person.
- ApprovedBy Alex Morgan, by name.
- Done“Moved $60 a day to holiday blend and gift sets.”
What each entry records
- 1
One history per decision
Each proposal carries its own history, with a dated line per step: proposed, checked, approved or declined, done. It sits under the proposal in the inbox, beside what changed and why.
- 2
What ran without you, too
A change made within an agent’s permission is recorded like one you approved: who proposed it, why, the checks and what changed. A stopped proposal is kept with the rule that stopped it, which shows you what agents tried.
- 3
The agent’s own account
Each agent’s notebook lists its decisions with their status: approved by you, ran automatically, or in progress. Your guidance sits beside them, with when it was picked up, so the reasoning stays with the history.
- 4
People’s changes, too
Changing a guardrail, publishing a brief, giving guidance, approving a delivery, adding to the library, inviting someone: each is recorded with who and when, and the libraries show recent changes.
Last week’s decisions, in orderOne example, in order
Oct 19 · Stopped
Proposed by the Reorders agent: 25% off a second order. Stopped by your content rules, which allow no discounts: “Offers a discount; none allowed.” You left a note the same day: “We don’t discount our coffee. Free shipping is as far as we go.”
Oct 21 · Approved
Proposed by the New Customers agent. 2 checks passed · reallocation needs approval. Approved by Alex Morgan. “Moved $60 a day to holiday blend and gift sets.”
Oct 26 · Ran automatically
Brand review rewrote two ads that made a health claim. Two checks passed and its rewrite reads adjusted; it went ahead under Acts and notifies you: “Made 2 changes.”
Oct 28 · Accepted by the Copy desk
Three subject lines for the running-low note, requested by the Reorders agent and delivered by the copy desk. Two checks passed, and the desk accepted them into the library under Acts and notifies you.
What the record always holds
Code records each step as it happens, and no agent can edit it.
Who proposed it and whyFixed
The agent or person, and their stated reasoning in their own words.
What the rules decidedFixed
Allowed, and under which permission level; waiting for a person; or stopped, with the reason.
Who approved or declined itFixed
By name, with their note if they left one.
What happenedFixed
The change that was made, or why it wasn’t, such as an item that was no longer approved when the launch ran.
Stopped proposals are keptFixed
A proposal the rules stopped is kept with the rule that stopped it.
When someone asks why
What happens when you ask an agent why it did something?
Open the decision. It shows the agent’s reasoning, the checks, who approved it and the notebook entry behind it.
What happens when a person changes a limit?
It’s recorded with who changed it and when, just like an agent’s action.
What happens to a stopped proposal?
It stays in the history with the rule that stopped it. Filter the inbox’s history by Stopped to see every one.
Can an agent edit the record?
No. Agents can only propose actions. The record is written by code as each step happens.
Is it written for engineers?
No. Decisions read as plain sentences in the inbox history and each agent’s notebook. Changes to guardrails and people are recorded with who made them and when.
Does it record what people do, or only agents?
Both. Decisions, guardrail changes, briefs, guidance, library changes and invitations are all recorded with who made them and when.
Ask “Why did you do that?” and read the answer.
Your work email is all we need to start.