Every action arrives as a draft with its evidence attached.

Proposals carry numbers, not claims

The model writes the reasoning and chooses which tools to call; it does not compute CAC, ROAS, margin or attribution. Every figure is stamped with the service that returned it, the window it covers and the attribution rule in force, and revenue attribution assigns to a channel is labelled as credited to it, never as caused by it. Disagree with a number and you can trace it to the service that returned it instead of to a sentence.

Approval is per action, not per batch

Every proposal is one reversible change carrying its own policy check. You can approve the budget shift and reject the audience expansion in the same review without leaving a half-applied plan, because actions apply separately. Approved items execute immediately and appear in the change log under your name.

Rejections are recorded with their reasons

A rejected proposal is stored with who rejected it, when, and the reason chosen from the account's reason list. Should the same recommendation return, the earlier rejection sits beside it. Someone joining the account in month six can read why this account does not do a particular thing.