It perceives, it reasons, it acts — and it knows where it may not.
Four things, and the fourth is the one that matters to the person who signs.
Work reaches it in any form.
You type. You speak. A file arrives. Another system sends something. None of these is a special case.
MAIA reads what turns up in the form it turns up in, and keeps hold of where it came from.
It does not bring a vocabulary. It uses yours.
One reading, every domain.
An invoice, a contract clause, a production schedule, a regulation, a message from a supplier. To a company these are five different objects handled by five different departments.
To MAIA they are one kind of thing: something bearing on what it may now do.
It reasons across the institution, not within a function.
The rule that governs a payment may live in a contract, a policy and a statute at once. MAIA applies all three to the same decision, in the same pass.
And it can say which one bound the outcome.
The grant.
Every procedure carries a grant: what MAIA may settle on its own, and what it may not.
Inside the grant, MAIA does the work — buying, scheduling, reconciling, drafting, replying — and carries the result into the systems the company already runs.
Outside it, the work is still done. It is done in full, and withheld, and a person is named.
The grant is set by the company, and only the company changes it. The line does not move because the model is sure.
It acts in the systems the company already runs.
Where a company runs something MAIA does not contain, MAIA reaches it through whatever that system exposes. Action means the ledger moved, the order went, the reply was sent.
It is not a report recommending that someone move the ledger.
MAIA Brain
See what a decision looks like.
Every action carries its reasoning with it. The clearest case is the one MAIA completes and then declines to commit.