Blog
-
computing costs
What did we lock in? Let the model read the contract and code do the math
When a provider raises its hourly GPU price, only part of your bill moves. The reliable way to find out which part: a model extracts each agreement into a typed schema with a source pointer on every field, and deterministic code computes the exposure in integer cents.
-
fixed assets
What walks out the door when your lab lead leaves?
What a team knows about each machine sits in several places, and one of them is a person. A $60,000 robot arm and a $4,200 repair show what it costs when that person moves on, and the one-page habit that keeps it.
-
fixed assets
What would an AI agent do with my paperwork? Put the permissions in the API
A coordinator that holds no data tools, specialists with narrow tools, read-only credentials enforced by the server, one tightly scoped write path with a signed agent identity, and an append-only log. One week of equipment paperwork, traced through each layer.
-
fixed assets
Why the register and the floor disagree by March, and how to build intake that keeps them in step
The register says 42 robots and the floor has 37. The fix is an intake path where a fixed graph runs the checks, the model gets one narrow slot, code can only make its answer stricter, and a person saves the record.
-
fixed assets
What does the lender want on the equipment schedule?
An equipment lender approves financing against a list, one line per machine. Here is what goes on each line, where each field comes from, and how to keep your list accurate when someone asks for it.
-
fixed assets
Why the arm is worth less on paper
Three numbers describe the same robot arm, and none of them is wrong. Here is what the one on your balance sheet is actually measuring, and what it is good for.