Chemicals and materials

Who signs the batch release when an agent did the checks?

Batch records, safety documents and supplier checks carry real risk. LeafCraft keeps a named owner on every decision and a record your auditors can open.

One teamYour rulesYour memoryYour budget

Book a demo Experience now

Record · Batch B-5520 releaseKept in your database · unchanged since written

Export JSON / CSV

07:30:01

Batch check agent

Ran 14 release checks against the specification.

Why: All within limits. Two near the upper bound, flagged.

07:30:02

Batch check agent

Passed to Dr. Kavita Rao for release.

Why: Release needs a qualified person by rule.

09:15:40

Dr. Kavita Rao

Released.

Why: Reviewed the two flagged values. Within spec.

09:15:41

Audit agent

Checked the decision against the rules. Passed.

Why: Qualified signatory. Maker and checker differ.

Cost of this task3.20limit 8.00

OwnerDr. Kavita Raonamed, never "the system"

ChecksPassedno one checked own work

Product screen · example dataLeafCraft console

Trusted by

What's changing in chemicals and materials

Batch release is a signature

An agent can run the checks. A qualified person signs. The record must show both.

Compliance documents by country

Safety data sheets, permits and declarations change by market. Agents draft them. People must own them.

Procurement under price swings

Raw material agents react to prices. A limit per agent keeps a swing from becoming a commitment.

Two risks the layer removes

The agents you can't see, and the model that gets retired.

Agents you don't know about

In chemicals and materials, agents arrive through vendor updates and team pilots. LeafCraft finds all of them, gives each an owner, and brings it under your rules or removes it.

Inside software you buySwitched on by vendor updates

CRMERPHR systemService deskOffice suite

Built by your teamsPilots, scripts and side projects

LangGraphCrewAINotebooksAutomationsCopilot studios

LeafCraft connects to your ecosystem and finds every agent

One registerexample counts

23found

9no owner yet

11governed

3retired

How discovery works

A model that gets retired

An agent built straight on one model has to be rebuilt and re-approved when that model is retired or repriced. On LeafCraft you switch the model for that agent in config and keep everything else. Months and a budget, saved.

Agent tied to one model

The model is retired or repriced
Prompts, tests and sign-offs rebuilt
Months of work, a new approval cycle
The history stays with the old tool

MonthsA rebuild budget

Agent on LeafCraft

Pick another model for that agent
Switching is a config change
Test it against your own record first
Rules, limits, owner and memory stay

HoursNo rebuild

TimeHours to switch, not months to rebuild

CostNo rebuild budget, no new approval cycle

MemoryThe record carries over to the new model

Your choice of model

Why it matters now

In chemicals and materials, the agents arrived before the rules did.

Chemicals and materials companies work under rules written by regulators, not by vendors. An agent may do the checks, draft the document or propose the order, but a named, qualified person signs the release and owns the declaration. The layer makes that separation explicit, enforces it on every run, and keeps the record inspectors expect.

What the record answers hereWho released each batch, who owned each declaration, and what the agent checked.

How the layer works

LIMS and QMS plug-ins

Compliance document tools

Procurement bots

Lab and plant laptops

No shared owner · no shared limit · no shared record

LeafCraftone layer, on your side

One ownerper decision, AI or person

Your ruleson every run

Your memoryboth reasons, your database

Your budgetset before work runs

The core infrastructure

What LeafCraft runs for chemicals and materials.

One team

Deviations and complaints go by impact to named people: the QA manager, the plant head, then senior leaders.

How it works 02

Your rules

You decide what review and document agents may clear alone, what must go to a qualified person, and what they may never do, such as release a batch.

How it works 03

Your memory

Every batch, document and supplier decision is kept with the reasons of the agent and the person, unchanged on your side for audits.

How it works 04

Your budget

Every batch check, document and agent has a cost limit set before the work runs.

How it works

AI and people, one team

Your chemicals and materials team, with AI on the org chart.

Does the work

Decides

Checks

AI drafts. A person decides. Another agent checks.

The agent prepares the case. Your person makes the call and writes why. A separate audit agent checks the decision against your rules.

Same rules for every seatNo one checks their own workOne named ownerCost set before it runsBoth reasons recorded

No one checks their own workAgent or person. Maker and checker are never the same.

One named owner per decisionNever "the system".

Authority earned from the recordWidens with clean work. Narrows after mistakes.

People stay where they workSlack, Teams, WhatsApp (coming) or email. Their reply moves the work on.

What changes for you

Today

With LeafCraft

Checks and release by the same agent

The agent checks, a qualified person signs, both on record

Compliance documents drafted with no owner

Every document has a named owner and a checker

Procurement agent commits during a price spike

Above its limit, it waits for the category head

Inspection trail rebuilt from emails

The record is complete the day the batch is released

Silence is never a yesEstimated before it runsNothing erased after it's written

Escalation pathBy complexity and impact. Named people, clear thresholds.

Edit

Team member · Neha Kulkarni · Regulatory affairsA document for a new market, or a flagged value

Waiting

Manager · Dr. Sameer Joshi · Head of QAA deviation, or no reply in 8 hours

Backup set

Senior leaders · Compliance head and CEO officeA regulatory notice, or a new kind of risk

Backup set

Silence is never a yes. If no one replies in time, the work moves up the path. Nothing is paid, sent or changed while it waits.

Product screen · example dataLeafCraft console

LeafCraft sells no agents, no models and no compute.

NeutralGains nothing from your choice of agent or modelYoursRuns in your cloud, VPC or on-premOpenAny model, any cloud, MCP and A2AEqualBought, built and people, same rules

Why that matters

How it helps your people

Who it helps in chemicals and materials.

Leaders who ask first

COOs and supply chain headsWhat happens when an agent changes a PO or a supplier order at 2am?Read Risk, compliance and auditWhen I ask who approved this, can anyone show me the full trail?Read CIOs, CTOs and IT headsVendors shipped agents and my teams built others. How do I govern all of them from one place?Read CISOs and security teamsHow many non-human identities do we have now, and what can each one reach?Read

Functions where it runs

Supply chain and procurementWhat stops an agent from changing a supplier order it should not?Read Sales and tradeWho approves when an agent changes a price or pays a claim?Read IT operationsAgents can now grant access and change cloud settings. Who checks them?Read

Questions teams ask

Can the record be changed after the fact?

LeafCraft's ready-made templates end every flow with an audit agent that writes to a log that cannot be changed once written. Run records sit in your own database.

Our formulations are confidential. Where does our data go?

LeafCraft runs where your data lives: your cloud, your VPC or on-prem. Keys stay in a vault, and outside agents get only the fields you choose.

Can an agent ever release a batch on its own?

Only if your rules say so. You decide what each agent may do alone, what needs a person and what it may never touch. Anything not on its list is refused before it runs.

Bring one chemicals and materials process.

We'll map it with you: which roles are AI and which are people, who decides, who checks, what it costs and what gets recorded.

Book a demo Experience now