Amon Sul is a deterministic execution layer for decision-heavy processes. Records only move along transitions defined in the active policy version, every step is written to an append-only log as it happens, and any past decision can be replayed under the policy that governed it. It is not a workflow builder, BPM suite, or AI orchestration layer.
Open product reference →Some processes have to hold up later: a warranty claim, a credit, a recall. When the rules live in scripts and ERP customising, nobody can say afterwards why a record moved, or prove it moved the way policy said it should. Amon Sul makes the policy the thing that executes.
What It Does
- Every state is a real one. A record is in a state the active policy defines, or it cannot proceed. Nothing waits in limbo between scripts.
- Nothing moves without a rule. If a transition is not in the active policy version, the system refuses to advance. Code cannot override governance.
- The log is the execution. Each entry is written as the decision is made, append-only, with the exact input, output, and policy version.
- Replay any decision. Reconstruct any outcome from any point in history, under the policy version that governed it, or see how today’s policy would decide it.
Where It Fits
Amon Sul is the lifecycle engine behind VMS: claim lifecycles, ERP postings, and the closing update back to VMS run as Amon Sul sequences. It can also govern processes of your own, calling your ERP and other systems at each step.
What It Is Not
Amon Sul is not a workflow builder, a BPM suite, or an AI orchestration layer. It is the layer that decides which transitions are legal, executes them, and keeps the evidence.
Where It Fits
Amon Sul works with Standalone SaaS and replaces business rules scattered across scripts, spreadsheets, and ERP customising that nobody can replay or explain later. The product gives operating teams a clearer workflow while keeping the system of record stable.
The important boundary is ownership. We define which decisions belong in the core ERP, which belong in extensions or integrations, and how support teams keep the model clear after delivery.