Skip to main content

Your agent planned to take payment before checking stock.

Check each plan before your agent runs it, so a wrong step is caught while it is still words.

How do you check an AI agent's plan before it runs across your systems?

You write the rules for a plan, such as reserving stock before taking payment and an approval step before anything irreversible. Your agent submits its plan to Vindex before the first step, and an independent model rules on it, naming any rule it did not pass, so a wrong step is fixed while it is still words.

  1. You write the rules

    Operations Manager and Owner

  2. Your agent does the work

    Step-by-step plans that touch more than one system, such as order to inventory to shipping to accounting.

  3. Vindex rules on it

    An independent model checks each output against the rule version in force and names any rule it did not pass.

Each branch checks the others. The agent never reviews its own output.

The rules you write

These are examples to adapt. Your company drafts, versions, and owns every rule, in plain language or from public rules. An agent can draft a rule. Only a person makes it law.

  • Order of steps

    Inventory is reserved before payment is captured, and parts are confirmed before a job is scheduled.

  • Approval first

    Every step that sends money, messages a customer, or deletes a record comes after a named approval step.

  • System named

    Every step names the system it changes and what it changes.

  • Totals agree

    The order total, invoice total, and ledger amount in the plan are the same.

  • Promised dates

    Any date promised to a customer is no earlier than the lead time stated in the plan.