> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cast.digitalfinancehq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What CAST is not

> The boundaries we draw on purpose.

Being precise about what CAST does *not* do is one of its most credible features. It pre-empts the objections a skeptical reader brings, and it keeps the claims defensible.

<CardGroup cols={2}>
  <Card title="Not an ERP replacement" icon="database">
    CAST sits alongside your existing accounting systems and produces posting-ready exports with the lineage hash in the memo field. The ERP remains the system of record for financial reporting.
  </Card>

  <Card title="Not workflow automation" icon="diagram-project">
    Workflows in CAST are consequences of events and policies — not the primary design object.
  </Card>

  <Card title="Not a fraud guarantee" icon="user-shield">
    CAST eliminates the class of fraud that depends on one party acting without the other's knowledge. It does not eliminate collusion — it makes collusion documented and detectable.
  </Card>

  <Card title="Not a point solution" icon="layer-group">
    The accounts-payable product is the first instantiation of a vertical-agnostic architecture, not the whole of it.
  </Card>
</CardGroup>

## The precise claim

<Warning>
  CAST proves the vendor confirmed these payment terms, for this specific payment record, at this timestamp, under this policy version, and that the record has not been modified since. It does not claim the underlying invoice is inherently real, and it does not eliminate collusion or onboarding fraud — those require upstream identity controls that CAST enforces as preconditions but cannot replace.
</Warning>

This precision is the point. A claim that is narrow and true is worth more to an auditor, a lender, or an insurer than a broad claim that cannot be defended.