# Amon Sul

Amon Sul is a configurable policy execution engine for applications that need
versioned business workflows and evidence of the work performed. It suits teams
connecting checks, calculations and external operations to explicit status routing.
The integrating application owns its records and business meaning.

An invoice review, for example, can run a required-data CHECK and route its result
to a status defined by policy. A CODE step can prepare data for a CALL or ODATA
operation. These are configuration examples, not preinstalled customer workflows.

## How work fits together

An **action** performs one operation. A **sequence** connects actions and maps
inputs and outputs. A **policy** offers sequences at statuses and interprets
their outcomes. An **entity** is a registered caller-owned object following that
policy. Published definitions are immutable; lanes separate execution records
and integration targets while sharing tenant definitions.

## Sign-in and workspace access

Sign in on your workspace address. Ask your administrator for a workspace
invitation and the required local roles. An account shared with Fleetlane
within the same provider environment does not grant access to this workspace;
sessions and product permissions remain independent. See
[sign-in and workspace access](https://docs.amonsul.io/guides/sign-in-and-access/).

## Before you begin

You need workspace permissions, published definitions and a lane binding for your
entity type. External work needs a lane-specific connection. API callers need
a scoped machine key. Composite screens and other controls depend on enabled
features. Execution does not guarantee receipt in another application; read
[execution limits](https://docs.amonsul.io/guides/execution-limits/).

## Evaluate a small workflow

1. Read [core concepts](https://docs.amonsul.io/concepts/core-concepts/) and [lanes](https://docs.amonsul.io/concepts/lanes/).
2. Follow [getting started](https://docs.amonsul.io/guides/getting-started/) with disposable test data.
3. Use [screens](https://docs.amonsul.io/guides/screens/) and [run a policy](https://docs.amonsul.io/guides/policy-execution/) to interpret evidence.
4. Review [policy examples](https://docs.amonsul.io/guides/use-cases/) and the downloadable [workflow JSON](https://docs.amonsul.io/developers/workflow-json/).
5. Connect your application with the [machine API](https://docs.amonsul.io/developers/api/) and [integration guide](https://docs.amonsul.io/developers/integration/).

The illustrated guides show existing local data. No policy execution, external
request or webhook receipt was exercised during the screenshot review.