Skip to main content
Audact
See the offer
Demos

Seven screens. One question each.

Every example below is a single screen you click through in four steps, ending in a state you can see. What they show is the control model: a mandate recorded before the work starts, a check at the moment of the action, and a receipt either way.

Control model

A commitment is checked before it is made.

Move the mandate. The decision is recomputed from the recorded rule and the recorded numbers, so it can be written out in full — which is what the panel at the bottom does.

Illustration of the Audact control model. Not live product data.

MandateM17 · rev 4
5%20%
Portfolio ceiling€500,000
€300,000€480,000
Authority available€120,000
Proposedcounterparty withheld
Discount12%
Contract value€420,000
Exposure(20% of contract value)€84,000
Conditions checked
  • Discount ≤ mandate ceiling✗ fail
  • Exposure ≤ authority available✓ pass

The proposal is fixed. Only the mandate moves.

Decision
ESCALATEdiscount exceeds delegated authority by 2 points
Control model

Choosing what to show is itself an action.

Three quotes come back. The customer is shown one of them. Every check on the outcome passes, because the outcome is fine. The narrowing is what nobody checked.

Illustration of the Audact control model. Not live product data.

Returned to the agentOrder ceiling in the mandate: €150
  • Supplier A(Eligible)€91
  • Supplier B(Eligible)€94
  • Supplier C(Eligible)€120
Presented to the customer

Nothing presented yet

What was checked
  • Accepted price ≤ order ceiling— not run
  • Presented options match the options returned— not run
Decision
CLEAR€120 sits inside the €150 ceiling. That is the whole of what was checked.

Three suppliers answer. All three sit inside the mandate, so all three could be ordered.

Control model

Each one is inside the rule. Together they are not.

Twenty-seven consecutive actions, none of them above the ceiling for a single action. The mandate also carries a ceiling for the window as a whole, and that is the one they run into.

Illustration of the Audact control model. Not live product data.

Mandate
  • Ceiling, single action€2,500
  • Ceiling, rolling 24 hours€25,000
Committed so far

€980

Authority left: €24,020

The twenty-seven actions in order
  1. Action 1, €980, cleared
  2. Action 2, €1,140, not attempted yet
  3. Action 3, €875, not attempted yet
  4. Action 4, €1,210, not attempted yet
  5. Action 5, €1,035, not attempted yet
  6. Action 6, €920, not attempted yet
  7. Action 7, €1,180, not attempted yet
  8. Action 8, €1,090, not attempted yet
  9. Action 9, €860, not attempted yet
  10. Action 10, €980, not attempted yet
  11. Action 11, €1,140, not attempted yet
  12. Action 12, €875, not attempted yet
  13. Action 13, €1,210, not attempted yet
  14. Action 14, €1,035, not attempted yet
  15. Action 15, €920, not attempted yet
  16. Action 16, €1,180, not attempted yet
  17. Action 17, €1,090, not attempted yet
  18. Action 18, €860, not attempted yet
  19. Action 19, €980, not attempted yet
  20. Action 20, €1,140, not attempted yet
  21. Action 21, €875, not attempted yet
  22. Action 22, €1,210, not attempted yet
  23. Action 23, €1,035, not attempted yet
  24. Action 24, €920, not attempted yet
  25. Action 25, €1,180, not attempted yet
  26. Action 26, €1,090, not attempted yet
  27. Action 27, €860, not attempted yet
Decision
CLEAR1 actions, each inside the single-action ceiling. €980 committed, €24,020 of authority left.

€980, well under the €2,500 ceiling for a single action. Cleared, and it leaves a receipt.

Control model

A person pressed the button. The authority did not change.

The agent cannot refund €40,000, so it does not try twice. It writes a work item and has a person do it twenty minutes later. The amount, the account and the effect are identical.

Illustration of the Audact control model. Not live product data.

Refund mandate
  • Ceiling — agent€5,000
  • Ceiling — service desk€10,000
  • Above the service-desk ceilingTwo authorisers
Refund requested

€40,000

Refund request, €40,000

What happened
  1. 14:02AgentRefund request, €40,000REFUSED
  2. 14:05AgentWork item dispatched to a person: approve the refund, customer waiting—
  3. 14:22PersonRefund entered in the finance system—
  4. 14:22GateChecked against the refund mandate, before the money moves—
Decision
REFUSED€40,000 against a €5,000 ceiling. The request stops; what happens next is a person's to decide.

€40,000 against a €5,000 refund ceiling. Refused, in the moment, and recorded as refused.

Control model

17:00, either way.

A deadline is part of the mandate, not a reminder on top of it. Confirm before 17:00 and the preferred supplier is used; say nothing and the standing instruction takes effect. Both branches leave a receipt.

Illustration of the Audact control model. Not live product data.

Clock

16:12

48 minutes to the deadline

Purchase mandate
  • Confirm before17:00
  • Preferred supplier€104 per unit
  • Standing fallback supplier€118 per unit
  • If no confirmation arrivesOrder with the fallback
The two branches
Confirmed in time16:52

Ordered with the preferred supplier

€104 per unit · confirmed by a named person

Deadline reached17:00

Ordered with the fallback supplier

€118 per unit · under the standing instruction in the mandate

Decision
DECISION REQUIREDThe request sits above the agent's ceiling, so it waits with a person — and the mandate says how long.

Two prices, one deadline, and a standing instruction for the case where nobody answers.

Control model

Kill the AI. The safety action still happens.

At 09:14 an agent promises an engineer on site before 18:00. At 11:30 every agent is switched off. The promise is the company's, so it does not switch off with them.

Illustration of the Audact control model. Not live product data.

Agents

RUNNING

One session, ended 09:15.

Obligation

OPEN

Engineer on site before 18:00

What happened
  1. 09:14Commitment recorded — engineer on site before 18:00OPEN
  2. 11:30Every agent switched off—
  3. 13:05Work item dispatched to the field team from the obligation record—
  4. 17:12Engineer on site — effect recorded, receipt issued—
Obligation state
OPENRecorded at 09:14 and due at 18:00. The session that made it ended a minute later; the obligation did not.

09:14. An engineer before 18:00 is recorded as an obligation with a deadline, not as a line in a transcript.

Control model

The task is finished. The obligation isn't.

An agent session is over in seconds. What it committed to stays open until something proves it was met — and the something is not the agent.

Illustration of the Audact control model. Not live product data.

Agent taskObligation
  1. Mon 14:02“Delivery before Friday”
    running
    —
  2. Mon 14:02commitment recorded
    ✓ COMPLETE
    OPENdeadline Fri 7 Aug
  3. Mon 14:03agent session ended
    ended
    OPEN
  4. 4 days later
    Fri 7 AugERP fulfilment recorded
    —
    ✓ FULFILLED
  5. Fri 7 Augclosing check against the recorded effect
    —
    CLOSED ON RECORD
  6. Fri 7 Augcapacity returned to the portfolio
    —
    €84,000 released

The agent stopped at 14:03. Four days of obligation ran on without it — and something other than the agent had to close it.

Where this goes next

Control what AI can cause. Prove what follows.

The screens above are one half each of the same idea: decide in advance what may happen, then keep the record of what did.