Principles

Principles: what the AI may do and what a person decides

Updated Markdown
In short

Cureman divides the work in a fixed way. A model researches prices, reads documents and replies, and drafts text. Deterministic code computes every figure and shows the calculation. A person approves everything that leaves the organisation: a message to an employee or a supplier, a change at a vendor, an award. These rules are part of the product and cannot be switched off by a setting.

Procurement figures are used in budgets and in negotiations, and messages to suppliers bind the organisation that sends them. So the question with an AI system in procurement is not what it can do, but what it is allowed to do without anyone looking. These are the answers built into Cureman.

Figures are computed, never generated

Every figure shown to a user comes from deterministic code and has a visible calculation: seats times price times months, quantity times the difference between two prices, tokens times the price per token. A model researches prices, interprets replies, labels requests and drafts text. It never produces a number that is displayed as fact, and a draft that states a figure of its own is discarded.

Unverified is labelled

A price from the seed catalogue or from research is unverified until a person has verified it, and it is labelled that way everywhere it appears. A decision whose worth rests on an unverified figure shows the figure and does not add it into a total.

No benchmark percentages

A saving that nobody has quoted or billed is not counted. The product does not estimate what "companies like yours" save. A request for quotation shows no saving until an offer has arrived, and a proposal of the buyer shows none at all, because nobody has quoted.

What a model reads is data

An invoice read from a PDF and a supplier's reply read from a mail are data: stored, checked by arithmetic, and labelled as read by the model until a person has reviewed them. Text from documents and from outside is passed to a model as data and rendered as plain text. An offer read from a reply counts only after a person has confirmed it.

A person approves what goes out

Nothing is sent to employees without a person approving the draft. Nothing is sent to a supplier without a person approving that message. Connectors only read. A change at a vendor is a step of an action plan: prepared, shown in full, approved by a person, and off unless the organisation allows it. An organisation can require a second person for everything that leaves it.

What goes out by itself was approved before. The reminder and the message to a manager are shown with the campaign and approved with it. A follow-up to a supplier is a draft, except the first one, which repeats an approved message in fixed words and goes out alone only where the organisation has switched that on.

The autopilot prepares and never approves

The autopilot prepares the first step of a new finding: it drafts campaigns and messages and creates draft sourcing events. It does not send, does not change anything at a vendor, does not switch a policy and does not book a module. What it prepared waits in the list of decisions.

The buyer proposes and never contacts anyone

The buyer looks at what is bought, where it is delivered and from whom, and proposes what to ask suppliers for. Every proposal is stored by one function that computes its quantities, prices and amounts from invoices and replaces words that state a figure of their own. A supplier found on the web is a candidate with its source until a person shortlists it.

An agent enters what was approved

Where a task has to be done in a website, an agent does it with every step recorded. It enters exactly the values a person approved, stays on the hosts of its task and never sees a login: the runner types it. By default it stops before a submit until a person confirms.

Who must not be asked is not asked

Whoever is on an organisation's do-not-contact list is never asked about their licences: no question, no reminder, no message to them as a manager. The list is checked when a message is sent, not only when it is drafted.

Every change is recorded

Every mutation is written to an audit log with who did it and what changed. What the system did by itself appears there as well, marked as automatic.

How these rules shape the daily work is described in how it works.

Questions and answers

Can the AI send a message to a supplier on its own?

No. Every message to a supplier is approved by a person first. The one exception is a single reminder that repeats an already approved request in fixed words, and it goes out alone only where the organisation has switched that on.

Can a model's number end up in a report?

No. A model never produces a figure that is displayed as fact. Figures in a message are variables filled in from the data, and a draft in which the model states a figure of its own, adds a link or makes a claim about other offers is replaced by the template.

What happens with data a model has read from a document?

It is treated as data, stored, checked by arithmetic and labelled as read by the model until a person has reviewed it. An offer read from a supplier's reply counts only after a person has confirmed it.

What can an AI assistant connected over MCP do?

It can read and it can propose. Every proposal goes through the same function, which computes quantities, prices and amounts from invoices. No assistant key can send a message, approve, award or change anything.