Most systems record what happened. MAIA records why.

Every action carries its reasoning with it: what was read, which rule applied, what authority it acted under. Not a log written afterwards — the decision itself, kept.

An account you can put your name under.

An audit asks three questions of any action: what was decided, on what basis, and by whose authority.

In most institutions the first is in a system, the second is in somebody's memory, and the third is inferred from a signature.

MAIA answers all three from the same record, because they were never separate.

A refusal is a result.

The clearest thing MAIA produces is not the work it completes. It is the work it completes and then declines to commit.

Not a system asking permission. A system that finished, and stopped.

Choose a ground.

The same decision, on four different kinds of work. The shape does not change, because the shape is what MAIA guarantees.

Each step names what it read and what it derived. The last two are the ones an auditor asks for.

Choose a ground.

A payment, prepared and refused.

Read
The obligation, the counterparty and the terms, each taken from the document that establishes it.
Derived
The sum, the treatment and the date it falls due, computed from what was read and from the policy that governs it.
Prepared
The posting, complete. Every line resolves to the source it came from.
Checked
The authority this procedure grants, against the sum prepared.
Refused
The sum exceeds the grant. Nothing is committed.
Routed
The named controller receives the prepared work intact, with the reasoning attached rather than summarised. The decision takes a moment, because the work is already done and the question is the only thing left.

An order, prepared and held.

Read
The requisition, the supplier record, and the framework agreement it is placed under.
Derived
Price, lead time and the terms that apply, from the agreement in force on the date of the order.
Prepared
The order, ready to send.
Checked
The category, the standing of the supplier and the value, against what this procedure may commit.
Refused
The standing of the supplier lapses before the delivery date. Nothing is sent.
Routed
The buyer receives the order complete, together with the lapse and the date that causes it.

A response, drafted and withheld.

Read
The clause, the obligations it creates, and the policy and statute that bear on it.
Derived
What the company would owe, and from when.
Prepared
The response, drafted, with every position traced to the provision that supports it.
Checked
The commitment against what this procedure may accept.
Refused
One term binds beyond the granted horizon. Nothing goes back to the counterparty.
Routed
Counsel receives the draft and the single term that stopped it.

A schedule, planned and not released.

Read
The order book, the state of the line, and the constraints in force today.
Derived
A schedule that satisfies them, and the cost of the one that does not.
Prepared
The plan, ready to release to the floor.
Checked
The change against what this procedure may alter without instruction.
Refused
The plan moves committed work past a date the company promised. It is not released.
Routed
The planner receives the schedule and the promise it would break.

MAIA Brain

AI you can put your name under.

Talk to us about what your company decides, and what it would take to account for every one of those decisions.