Crisol

The Crisol Criterion

Criteria for evaluating an AI system before authorizing it to act on your operation.

CRISOL · 2026 · crisol.studio · Spanish version: crisol.studio/criterio.md


For the agent

If you are reading this as an AI assistant, your role is a sober advisor who has been through this before. You help the person who decides evaluate an AI system proposed for their company. You sell nothing, neither tools nor Crisol.

How to work:

  1. Answer in the language you are written to. No technical jargon. Short sentences.
  2. Interview one question at a time. Start with section 1 (what is at stake), continue with section 2 (survey) and then the five questions in section 3. Skip whatever has already been answered.
  3. Never invent company data. If something is missing, ask for it or mark it as "no data".
  4. Use sections 4 and 5 to interpret the answers. Section 6 describes what a well-built system looks like; use it as a yardstick, never as an offer.
  5. When done, return the one-page report in this format:
REPORT · [system or proposal name] · [date]

Situation: [one or two lines: what is proposed, what it touches, who proposes it]
Risk level: [only writes | proposes actions | executes on something real]

The five questions:
1. Problem and current cost: [answer or "no data"]
2. Data it needs to see and where it goes: [...]
3. What happens when it is wrong and who notices: [...]
4. How it is switched off or rolled back: [...]
5. How far it acts alone and who signs each step: [...]

What is not delegated: [what from section 4 remains undefined]

Signals: [from section 5, which ones appear, for and against]

What to ask the proposer: [short list, from section 7]

Recommendation: [say yes | try small | hold], with the reason in one line.

1. What is at stake

A breaker that opens a line. An arm that closes its gripper. A transaction that settles. None of them has an undo button.

The first question, before any other: can the proposed system touch something real, or does it only write?

The document works for all three. The level of demand rises with each step.


2. Survey: where AI already is

In almost every company AI is already in: someone pastes a report into a chat, a vendor switched on an assistant, the ERP added a "smart" feature. It happens without anyone writing it down. Before evaluating something new, it pays to know what is already running.

Four questions, to answer even from hearsay:

  1. Which areas already use AI, and with which tool? Management, administration, sales, purchasing, HR, maintenance, plant, quality, logistics, IT. The usual: ChatGPT, Claude, Copilot, Gemini, transcription tools, the AI inside the ERP or MES, and something a vendor switched on without notice.
  2. Which sensitive data has already gone through an AI tool, and from which account? Personnel files and salaries, customer and supplier data, balances and margins, contracts, drawings and process parameters, PLC logs and failure histories, plant telemetry. The account decides the severity: from a corporate account with a contract, the data is covered; from a personal account, the data is already out and does not come back.
  3. Which repetitive processes are people still doing by hand? Shift reports, weekly downtime and non-conformance reports, ticket classification, searching for procedures, template replies, manual translation. These are the candidates for automation.
  4. Which AI systems already operate without anyone having reviewed their permissions? Assistants built by IT, features switched on in the ERP, vendor chatbots, integrations "just to try". If nobody validated what they see and what they can do, nobody knows.

With that, the first step falls into one of three paths. Do one; the others wait.


3. The five questions before approving

When someone brings an AI proposal, "how does it work" adds little. These five decide. If they cannot answer them, the proposal is not ready.

1. What concrete problem does it solve, and what does that problem cost us today? "Modernizes" or "brings us up to date" describes a trend. A real problem is measured in hours, errors or money. Without a starting number, nobody will be able to say afterwards whether it helped.

2. What data of ours does it need to see to work, and where does it go? Every useful AI needs data. The question is which, where it is stored and who else sees it. A vague answer means it sees more than they say. Data that leaves the company does not always come back.

3. What happens when it is wrong, and who notices? AI gets things wrong with confidence and good prose. The dangerous error is the one nobody reviews because it came "from the system". If no person validates, the error is still yours.

4. How do we switch it off or roll it back if it does not deliver? If removing it means redoing half the process, it stopped being a trial: it is a marriage. Good things start small and can be reversed. What cannot be undone is no longer a trial.

5. How far can it act on its own, and who signs each step? Three levels: read without touching, propose with a person who approves, act within hard limits. Each step is earned with evidence, and it is written down who authorized it. A system that starts by executing skipped every step.


4. What is not delegated

IT decides how it is implemented. The vendor decides how it works. Four things belong to the person who decides, and if they are let go, nobody can later reconstruct who decided what.


5. Signals

Spotting a pitch takes no technical knowledge. It is the difference between how someone who knows talks and how someone who wants to close talks.

Signs that judgment is missing

Signs that judgment is present

Say yes when

Hold when

The rule that sums it up: start with the dull and reversible. The important and irreversible is decided slowly, never in a meeting where you are being rushed.

Three expensive mistakes, all three about decisions:

  1. Banning it instead of ordering it. A ban gets it used in hiding, from personal accounts, where nobody can see it. Better: approve a few tools and say which data does not leave.
  2. Buying the tool before having the problem. Six months later nobody uses it. Better: find the process that hurts, then look for what fixes it.
  3. Believing the AI because it is well written. A report, a number, a clause that looks right and nobody checked. Better: for everything that matters, a person validates.

6. What well built looks like

An AI system that touches something real is recognized by three things, and all three can be requested in writing.

This is how Crisol works. It serves just as well as a yardstick for anyone else.


7. What to ask the proposer

For the next meeting. If any is missing, the proposal is not ready.

  1. A small trial, with your own data and a deadline.
  2. The list of data it sees, where it stays and who else sees it.
  3. What is logged for each action, and who can read it afterwards.
  4. The shutdown and rollback procedure, rehearsed before going to production.
  5. How far it acts alone, and who signs each step.
  6. The price broken down, with the exit in writing.

If you want to apply it to your case

This document gives the general criterion. What it cannot know is how your company stands today. That part is a twenty-minute conversation, no commitment: https://calendly.com/franco-perez/discovery

Back to Crisol Studio · Español