The document nobody followed up for.
A case looks active while the one thing required to move it forward remains unowned. Nothing flags it, because nothing failed.
The authority layer for AI workers
Delegate the work. Keep control.
Veridom establishes which company rules apply, who can approve and what evidence is needed, then checks proposed AI actions against that understanding.
What you establishRules your workflow can rely on
What is accountableThe decision
What you keepThe operating model
Default behaviourRespect the boundary
How work endsEvidence recorded
01 · The first workflow
For the team that has to decide whether a payment can move.
A payment exception sends an operator back through the policy, the approval matrix, the customer terms and the case evidence. The answer may depend on a temporary delegation or an exception someone agreed last month.
Veridom gives the team a reviewed account of what applies, so each new case does not start with the same reconstruction. Unresolved questions stay visible. When governing information changes, recorded dependencies identify work that needs another review.
We are starting with payment-operations teams and one bounded exception process. The pilot measures how much review and maintenance this takes, and whether the team wants to keep using the model.
Explore the payment-exception pilot →02 — The operating failure
Work rarely fails at the moment of action.
It fails between intent and completion. Knowledge is fragmented, authority is unclear, exceptions are undocumented, and nobody persistently owns what happens next.
People close those gaps today because they have history with the company. They know which rule really applies and who genuinely decides. AI does not.
1
Days open
Nothing failed
Nobody was negligent
Nothing failed
Nobody was negligent
The approval with no legitimate owner.
Capability exists. Permission does not. And a person being present is not the same fact as a person being authorised.
The expired rule still governing.
Retrieval finds it perfectly. Reality moved on eleven months ago, and nothing marked what depended on it.
The exception everyone assumed someone else was handling.
Most operational failure is unmanaged waiting. The shortage is not intelligence. It is persistent ownership.
Agents don't become trustworthy by knowing more. They become trustworthy when the organisation becomes operable under delegation.
03 — The difference
Your rules should not be reinterpreted for every action.
Veridom connects the evidence behind a rule to its review, the action it governs and the work that needs reconsideration when it changes. That connection is the centre of the product.
Evidence becomes a reviewed rule
An interpretation becomes usable only through an explicit review and activation path.
The source, its scope, unresolved questions and the reviewer’s decision stay attached to the rule.
What changes: the team reviews a specific interpretation with its supporting evidence. Accepted rules can be reused; unresolved questions do not become permission.
Authority is checked for this action
Being able to act is not the same as being allowed to act.
Routing, authority and permission stay three separate facts, each inspectable on its own. Collapsing them is how a company loses the ability to prove which one actually happened.
What changes: exceptions arrive ready for a decision. A person receives the issue, the evidence, the authority required and a recommended next step, not another context-hunting task.
Changes reach dependent work
Expired knowledge cannot quietly keep governing.
A registered amendment preserves the earlier record and identifies affected dependencies. Work relying on stale governing state returns for review.
What changes: a policy that has moved stops being quoted back to you as current, and recorded dependencies identify conclusions that need reconsideration.
Credit & collections policy — v3
Superseded
Credit & collections policy — v4
Governing
The decision keeps its evidence
What governed and what happened remain connected.
The proposed action, governing version, checks, approval and execution outcome are recorded together. A completed receipt and an unresolved case remain distinct outcomes.
What changes: the case moves with its context attached. Evidence, decisions, approvals, communications and system state travel together across every handoff.
See it in action
One payment exception. A worker, a reviewer, a record.
Follow a payment exception from investigation to separate approval, ACE checks and a completed evidence record. See where the worker proceeds, and where it stops.
ALEX maintains the understanding. ACE checks the action.
Ask your company a simple question.
You will get several answers, all sincere, all from real places. That is not a documentation problem. It is the reason you cannot hand this work to an AI yet.
What your company says today 4 answers
What unreviewed retrieval can miss
No date checked · no authority checked
What ALEX returns
Not resolved
Example questions and sources. One governing answer, where it came from, and anything still contested surfaced rather than averaged into it.
Something has to know how the work actually runs.
Before AI can be trusted with consequential work, it needs a current, evidence-backed account of how the organisation genuinely operates, not how the handbook says it does. That is what ALEX builds, and keeps current as the company changes.
The part that matters is what it refuses. Where two sources genuinely disagree, it will not pick one to sound confident. It tells you, and it says who has to settle it.
Meet ALEX →06 — Where to start
Start with one consequential workflow.
Our first offer is an eight-week, USD 7,000 pilot for one operational payment-exception process. We review the model together, replay historical cases and measure the effort needed to keep it useful.
The first operating model
- The real workflow, and its legitimate endings
- Authoritative sources, and where they contradict each other
- Decision owners and the limits of their authority
- Exceptions, waits, and evidence that is missing
- Which work is human, which is AI-assisted, which is AI-executable
- The first governed execution design
Week 1–2
Understand
Map where work stops, what evidence is missing, who holds real authority, and what currently governs.
Week 3–4
Authorize
Agree the boundary: what the Worker may do alone, and what always routes to a named person. You set the line.
Week 5–8
Replay
Replay historical payment exceptions with separate approval, simulated execution and evidence records. Measure corrections, review effort and change impact.
Close
Prove
One meaningful contradiction, one correct refusal, one completed case, with the evidence behind each. Then you decide.
Still deciding which way in? Explore the Order-to-Cash illustration → See what ALEX establishes →