What Birdie cannot do

Nothing spends without a person's decision. Starting or resuming spend is a click by a named person, every time. A budget raise is too, unless you give a client a bounded band: inside it the server, never Birdie, may raise a budget that is already delivering, never above the 20% line, and reports every raise the same morning.

Everything is created paused. There is no way to create something live. Switching it on is a second, separate approval.

A raise of more than 20% in one change shows both figures on a second screen before the button works. A raise from zero always does.

Before and after are always shown, on the approval and in the record.

A change to more than five things needs one approval that lists every one of them by name.

Reading is free. Reports, lists and figures never ask for confirmation.

Each client has a daily warning line. Crossing it is allowed only after a person confirms the specific number on screen.

A client can be set so their own sign-off comes first. Until they approve the preview, nothing runs, and there is no override.

Every decision is on a chain you can export, every entry with its hash. Exporting the chain is itself on the chain.

Your team can tighten any limit. Loosening one past the defaults takes the platform's administrator, and that change is recorded too.

Birdie has no back door. It calls the same checks as the screen you use, and it can only read, sync and propose. At worst, a misled model creates a proposal nobody approves.