Spark ERP

AI · Trust

Prove a change is better before it reaches anyone.

Evaluations run the same test questions through a prompt or pipeline and score the answers, so you can compare runs and catch regressions. Guardrails check what goes in and what comes out for personal data, prompt injection and blocked terms.

Evaluations and guardrails in Spark ERP Your ERP dataModel providerPermissions Your ERP dataModel providerPermissions Human approvalProposes Audit trailAsk or trigger
Evaluations and guardrails and its guardrails
Your ERP dataModel providerPermissionsAudit trailHuman approvalEvaluations and…
How Evaluations and guardrails works with you
Ask or trigger

A user request or event

1
Grounded

Uses your own records

2
Proposes

A draft, not a silent change

3
You approve

Within your permissions

4
Logged

Recorded for audit

5

Evaluations

Test questions

A set of real questions with what a good answer contains.

Scorers

Contains, does not contain, exact match, pattern, a field of a JSON answer, or a model as judge.

Compare runs

See which cases got better or worse between two versions.

Guardrails

Personal data

Emails, phone numbers, ids and payment card numbers (card numbers must pass the standard check, so an invoice number is not flagged).

Prompt injection

Attempts to override the instructions are caught.

Flag, mask or block

Choose what happens when a check finds something. Available on agents, pipelines and workflow steps.

The real screens

The runs of an evaluation showing that 2 of 2 cases passed against a pipeline.
An evaluation run: two of two cases passed.
The guardrails tab of an agent with switches to check the request and check the answer.
Guardrails on an agent.

What to know today

Guardrails are pattern checks and are one layer, not the whole of security: permissions on tools and data remain the real control. Evaluations run while you wait and do not yet block a release automatically.

Release AI with evidence.

Bring a few real questions and we will show you a run.