How Definite fits into your stack

Definite sits alongside your finance systems and processes. It reads from them, verifies against versioned rules, and produces evidence — it never writes back.

Read-only connections

Sources connect read-only: ERP and ledger systems, banking and billing platforms, data warehouses and BI, and documents and spreadsheets. Ingestion works from scheduled file drops, read-only APIs, warehouse connections, and direct document upload. Every ingested source becomes an immutable snapshot with a content hash; runs bind to snapshots, not to live systems.

Control plane: Vault

Vault is the tenant-isolated system of record. It stores workflow programs and their versioned definitions, runs and their ordered stage events, exceptions and reviews, artifacts with lineage, signed receipts, and the per-tenant Merkle audit ledger with signed checkpoints. Tenant data lives in per-tenant databases; credentials and transport keys stay in a secret manager, never in application rows.

Agent runtime

A stateless compiler and agent runtime performs the map, investigate, and assemble work. It holds no database and never stores source documents; it receives bounded, declared inputs per request. Model identity, usage, attempt, and provenance attach to the workflow run's event stream. Models come from an approved per-tenant catalog. No agent can emit a verdict.

Deterministic engine

The check stage executes the rule versions bound to the run. The same inputs and the same rule versions always reproduce the same PASS, FAIL, or CANNOT_VERIFY. Numeric checks run in exact arithmetic — a figure that cannot be read exactly yields CANNOT_VERIFY with a reason code rather than a guessed result. Every check writes a signed receipt.

Console

The console at app.usedefinite.com is where your team prepares reconciliations, reviews exceptions and approvals, inspects evidence and lineage, and administers connections, definitions, members, and API keys. See the console overview.

Your boundary

Definite does not write to source systems, initiate transactions, or file with a regulator or counterparty. Your team reviews, approves, signs, and submits its own outputs. Final exports require a named human with an admin or owner role; agent drafts never become reviewer-facing conclusions on their own.