Decision assurance for regulated firms

Everyone shows the source.
We show you who may sign it.

AI can prepare a quarter's work in minutes. Finishing it still means showing the rule that applied, the evidence it rested on and the authority behind it. Provenact carries that work through to its outcome inside your own approved rules — and the proof falls out of doing it.

Request a working session See a real receipt
Decision record · Investment mandate review
  1. The rule

    Covenant exposure may not exceed 50%

    Mandate v5.0 §4.3 · put in force by your firm
  2. The evidence

    53% worked out in code from the holdings snapshot

    Not a model's opinion
  3. Who may decide

    Head of Investment Risk

    The operator may prepare the case. Only this person may decide it.
  4. The outcome

    Carried out on that person's authority, and recorded: what, how, why and when.

    The receipt is the proof. It falls out of doing the work.
In design-partner preview · not generally available

How it enters a firm, and what it does there

From mandate to outcome, step by step.

Every firm runs on a mandate

Its approved intent, its rules, and who may decide. Provenact starts there.

  1. Every firm runs on a mandate. Its approved intent, its rules, and who may decide. Provenact starts there.
  2. Nothing gets in until the firm says so. Security, risk and the accountable person each approve their part. Some systems are marked never.
  3. One job, and only what it needs. Choose the outcome. Two systems open, to read only.
  4. The work runs inside your rules. A check done in code finds 53% against a limit of 50%, and the breach goes to the person entitled to decide.
  5. The outcome, with its proof. The decision is carried out in your own system, on that person's authority, and the receipt records what, how, why and when.
  6. Each job leaves the next one easier. The decision joins the firm's memory, and the same mandate carries the next workflow.

The limit on AI was never intelligence. It was proof.

01 — The problem
+440%

rise in median review time once AI tooling arrived. Output went up. Review capacity did not — and the pilot died in the review queue rather than in the model.

Faros AI · 2026
95% of enterprise AI pilots fail to show a return MIT · 2026
21% have a mature way to govern it — against 74% adopting Enterprise surveys · 2026

Show us what the AI produced.

02 — What it does first

Give Provenact the draft and the approved sources it was meant to rest on. Every claim comes back carried by an exact source span, unsupported, or stale — with a prepared correction and the name of whoever is permitted to approve it.

The Fund returned 8.4% over the quarter, ahead of its benchmark. Covenant exposure remains within the limits set out in the mandate.

Carried by an exact source span Contradicted by a deterministic check Two more kinds — unsupported and stale — are on the next page See the full example and its exception list

One governed chain

03 — How it works

Provenact is not a checker bolted on to somebody else's tool. It takes your controlled documents, turns them into rules your people review and put in force, then runs the workflow against them — and every stage leaves its evidence behind it.

  1. Sources
  2. Meaning
  3. Rules
  4. Procedures
  5. Connections
  6. Authority
  7. Outcome
  8. Receipt
01ConnectControlled source intake. Origin, version and permitted evidence — with honest empty states.
02ReviewSource-linked rules and distinct human decisions. Correction and undo. Nothing self-activates.
03AuthoriseThe authorisation set, the allowed and forbidden AI boundary, and a named-human gate.
04OperateProvenact does the work to an outcome-led plan with a budget and stopping conditions. It acts only on a named person's recorded authority.
05VerifyReconstructs the persisted chain: receipt identity, matched lineage, explicit not-covered states.

The model may interpret, propose and prepare. It may not invent facts, legal force, status, authority or execution.

If the screen can compute the answer, the answer is decoration.

Rule to receipt to action.

04 — What it is for

The aim is not a better checker. It is work finished, with your people able to see the what, the how, the why and the when of every decision. That is what lets an organisation trust AI enough to use it. And it applies wherever work runs from a mandate to a decision, an approval and an outcome.

  1. 01 · The mandate What you intend, and who may decide. Your policies, your procedures and your approval authority, turned into rules your people review and put in force.
  2. 02 · The decision The work, done inside those rules. Provenact reads the sources, applies the rules in code, prepares the case and raises whatever needs a person.
  3. 03 · The approval The right person, and only them. The decision goes to whoever holds the authority for it. No one else can make it, and it is recorded as theirs.
  4. 04 · The outcome The act, carried out and proven. Provenact carries out the decision in your own systems, reads the result back, and seals the receipt.

Nothing acts without a named person's approval. Every decision then joins the memory your organisation keeps, so the next job starts further ahead.

05 — What the firm keeps

Every correction becomes part of your operating memory.

Exceptions do not disappear once resolved. Each becomes an approved instruction, attached to a named person and a version. After a few cycles that is a written record of how your firm actually decides — and it is the part you keep.

Approved operating memory
  • R-014Orders handled excludes trades booked after the 17:00 cut-offA. Whitfield · 12 Mar
  • R-021AUM is taken from the quarter-end valuation file, not the daily feedA. Whitfield · 14 Mar
  • R-033Any movement over 25% needs a recorded explanation before sign-offR. Deane · 2 Jun
  • R-041Revenue reconciles to the ledger, not to the management packR. Deane · 4 Jun

It is yours

Text, not weights

Readable, editable, exportable. Change the model next year and it survives intact, because it was never in the model.

It compounds

The next job starts further ahead

Source, authority and evidence structures carry forward. Each new workflow still receives its own substantive rules and checks.

It outlives people

If they leave, it stays

What lives in one experienced person's head becomes text the firm owns. A new compliance officer inherits it, not a handover call.

Citations are table stakes. Authority is not.

06 — Why us

A citation tells you where a sentence came from. It does not tell you whether this person may sign it. Those are different questions, and only one of them is widely answered. Three things have to travel with the work.

The rule

Your approved rules, versioned

Reviewed by your people, put in force in a named ceremony, and anchored to the exact span of the document each one came from.

The authority

Who may approve, and under what mandate

The approval matrix and the delegation become a versioned object you own and edit — not configuration inside our product, and not a step in a workflow.

The proof

A record a later reviewer can reconstruct

What was decided, on what evidence, by whom — and, stated plainly, what was not covered. The step that checks the work is not the step that produced it.

The first of those is now common. The second we could not find answered in any published material we were able to reach. Several products route work to a reviewer; we could find none that treats delegated authority as data the institution owns and versions.

07 — The next conversation

One recurring decision. One working session.

Not a demo. We take one decision your firm makes over and over and work through what it would take to make its basis reconstructable — with the person who owns the procedure in the room. Ninety minutes is enough to tell whether this is worth a serious pilot.

Request a working session Where we are, stated plainly
P. Every act, proven

Know what applies. Know who may act. Keep the evidence.