Kraton / Document checks / source-backed demo

Check invoice math before it moves on.

Repetitive document checks do not always need another hosted workflow. A compact validator can inspect the fields you pass it, return a result, and stop within a known compute budget.

See how the Engine enforces limits Inspect invoice-validator

The trade-off

Keep the task. Narrow the handover.

A common pattern

A document may be copied into a separate service just to compare line items, totals, and a few supplied tax rules.

This Kraton demo

The invoice-validator demo checks a supplied invoice against its example rules inside the Engine and records fuel used by the calculation.

What is actually bounded

The boundary is part of the tool.

The example is useful because it makes the allowed inputs and actions explicit—not because it claims to solve every version of this task.

The component only sees the invoice data provided to its typed input.
Execution uses deterministic fuel accounting to bound the CPU path.
The caller can inspect the code, declared interface, and run result.

Where this example stops

The demo uses a small fixed set of example tax rates. It is not tax advice or a jurisdiction-compliance engine.

One scenario at a time

See another way to keep work in your hands.

All use cases