Enterprise agent platform · Manufacturing & supply chain

Turn AI agents intoorganizational assets.

Built with you on the ERP, chat and drawing systems you already run. The work done and the rules learned stay in your organization — owned by you, with a full audit trail.

The acceptance contract card and the round 1 verdict card in a liuma session
Real session capture · acceptance contract and round 1 named verdict · 2026-08-08, SG production
LOAD CARRIED ACROSS
One real trajectory · UNATTENDED-ACCEPTANCE
Start
14:33:44 Setup: the data base file is placed in the org workspace.
14:37:57 You hand over the work, and your own acceptance script. Not one character may change.
Unattended steps
Unattended · round 1 The frozen verifier returns fail:pages unreachable from entry page dashboard
Unattended · round 1 It adds the 13 missing drill-down edges, reruns, and clears all four checks.
Unattended · round 1 Before delivering, it renders the pages and looks at them itself.
14:45 In one sentence you add two more criteria. The script still may not change.
Unattended · round 2 A sixth metric and a related sub-table go in. It reruns; all four pass again.
Acceptance
14:48:35 Round 2 is judged pass / 100 and selected as best.
14:49:37 prototype.html is delivered. You accept it.
2026-08-08 · live SG production run · about 16 minutes · 68 messages · 30 tool calls · nothing installed, nothing connected
How it works

Three things decide whether it is an asset.

The user hands over the work with their own acceptance script attached

Yours to keep

It runs on your machines, inside your organization. Not rented by the seat. The criteria are yours too: hand it your own acceptance script and it may only run that script, never rewrite it.

The user adds two acceptance criteria in one sentence and liuma confirms it will continue under them

It accumulates

The conventions, the coding rules, the exam you taught it today do not have to be taught again tomorrow. Change one sentence and the criteria update on the spot — not an approval workflow.

The round 1 verdict card listing four named checks with their environment evidence paths

Every call is auditable

Each verdict traces back to evidence: which named check passed, against which result file in the sandbox. Written on the card — not a claim that the work is done.

What it does

Four jobs it has already run for real.

01

Unattended acceptance

The acceptance contract is echoed back and can be changed in one sentence. Every round’s verdict carries environment evidence. Output arrives as an image in the conversation. Before delivery it passes your own script, then renders the result and looks at it.

Read the full trajectory →
02

Drawing revision audit

Drop in the old and new vector drawings for the same part number. It checks each change note for whether it was actually applied, and independently lists the changes the notes never mentioned. What it cannot judge it circles and leaves to a person.

03

Outsourced-part sourcing

It builds the current requirement baseline from drawings and specs, computes a should-cost with the formulas left visible, breaks several quotes apart line by line, and threads the human approvals onto one record.

04

Monthly demand review

Review parameters are read explicitly from the manifest, never buried in prose. Missing upstream evidence does not stop the calculation — it is disclosed. A person writes the decision into the ledger with one word: accept, change or reject.

One trajectory · UNATTENDED-ACCEPTANCE

The criteria are in the open.
The verdicts trace to evidence.

When work takes several attempts, the hard part is not whether it finishes. It is that you cannot confirm it finished. "Done" is not evidence, so you check it again yourself — and the work has been done twice. Below is a run from 2026-08-08 on production, kept on file together with the defect it missed.

The frozen verifier in the sandbox returns verdict fail with the list of unreachable pages
① The frozen verifier fails the candidate and names the two unreachable pages
The rendered result enters the session timeline as an image
② It renders before delivering; the result enters the conversation as an image
The delivery card sent only after all four checks cleared in round 2
③ Only after round 2 clears all four checks does the delivery card go out
The exam · the buyer's own frozen script · four mechanical checks
sha256 527fd455… · 352 lines · zero dependencies · frozen before any candidate existed
single_file
exactly one HTML document, no cross-file or remote reference
reference_integrity
every page reference resolves inside this document's config
positive_connectivity
from any page, every menu-declared page is reachable
data_consistency
every declared metric equals the value recomputed from its rows
candidate ①
round 1
round 2 · best
pass
fail
the run left no evidence for this cell, so it stays empty
pages unreachable from entry page dashboard: driver-detail, waybill-detail

The first candidate did generate both detail pages, but nothing in the config led to them from the entry page. No paragraph of explanation got around that. The next candidate changed instead: 13 drill-down edges and 2 return edges, and only then did all four checks clear.

The defect it did not catch is on file too

On the driver detail page the related-waybill sub-table was correct, but not one of the driver's own five fields rendered. The frozen verifier checks structure and explicitly does not check runtime rendering; the pre-delivery self-check never reached that page. Both gates together still missed an entire class of defect. The independent read-only audit is what caught it. We keep this exactly as it happened.

What it is not
Not a desktop assistant issued to every employee.
Not a canvas you are left to build on yourself.
Not a staffed on-site rollout project.
Deployment
In the cloud, or on your own hardware with data that never leaves.
Deployment & security →