In a steel plant rail yard, demurrage is not a metaphor. It is a clock. Free time expires. Wagons sit. Commercial teams argue with incomplete radio logs while the tariff keeps counting.
We have watched programs try to "AI the yard" by letting a language model summarize rake status and, somewhere in the enthusiasm, start treating that summary as the detention record. That is how you lose disputes. Opposing commercial teams do not care that your model was eloquent. They care whether your timestamps are immutable and your free-time rules match the contract.
Demurrage clocks must be deterministic. LLMs may draft the dossier. They must never own the clock. That is Zero-LLM-Trust applied to plant rail—and it is the spine of Xenith Yard.
Why Yards Still Run on Radio and Logbooks
Heavy-industry internal networks are not public freight apps with clean GPS everywhere. Controllers juggle exchange yards, tipplers, blast furnace and SMS moves, finished goods, and hazard tracks. Status updates arrive late. TAT is hard to measure. MIS reports get typed from registers after the shift.
Documented pain patterns we hear repeatedly:
- Rake lifecycle visibility lags reality by hours
- Demurrage accrues beyond free time without a single trusted timeline
- Shunt plans live in heads and whiteboards
- Hazard tracks and crossings lack continuous intrusion monitoring with a human gate before sirens
Throwing a chatbot at that mess without event sourcing just creates fluent fiction. The industrial AI fix starts with lifecycle state and clocks, then adds language on top.
Anatomy of a Defensible Detention Clock
A dispute dossier that survives commercial review needs four ingredients.
1. Immutable event timestamps
Arrival at exchange, placement, tippler start/stop, release, departure—each event needs a time the system cannot quietly edit after the fact. If an admin can rewrite history, you have a diary, not evidence.
2. Configurable tariff rules
Free time and demurrage rates are commercial facts, not model outputs. Tippler free-time windows and per-wagon or per-rake hourly rates belong in a rules engine the commercial team can audit. Handbook tariffs vary by plant and contract; the architecture must parameterize them, not hardcode a demo number as truth.
3. Rake lifecycle as system state
The yard map and rake state machine are the system of record for operations. Radio remains a human channel; it should not be the ledger.
4. Human confirm on financial and safety actions
Interactive shunt planning with human confirm. Edge CV intrusion alerts with HITL before sirens. Billing and safety stay gated. Language models summarize evidence packs; they do not trip horns or invent hours.
This is the same commitment boundary we argue for sortation billing and fintech decisions in Zero-LLM-Trust. Money and safety are not prompt territory.
Where the LLM Still Earns Its Keep
Zero-LLM-Trust is not anti-LLM. Yard commercial teams drown in narrative work:
- Turning event chains into dispute letters
- Explaining why a rake missed free time using cited timestamps
- Drafting MIS commentary for leadership without retyping registers
- Summarizing intrusion alert evidence for safety officers
Those tasks are high leverage precisely because the facts are already fixed. The model is a writing surface over a sealed timeline. Pair that with Xenith Agents for multi-step dossier assembly and Xenith Seal when you need cryptographic non-repudiation on approval events.
What we refuse: "estimate demurrage with AI" as a product feature. Estimation is what you do when you lack events. Buy sensors, RFID/GPS roadmaps, and integration to enterprise identity—not a creative clock.
PoC Honesty Beats Theater
Plant rail programs often start with synthetic rakes and a yard map demo. That is fine if labeled. A useful PoC delivers:
- Live-looking rake lifecycle and yard map on synthetic traffic
- Detention clock rules engine with configurable tariffs
- Sample dispute PDF with an evidence chain
- Roadmap for RFID/GPS and enterprise IdP integration
- Explicit production hardening plan (availability, auth, connector depth)
What a PoC should not claim: full industrial readiness on day one, unlabeled "₹ recovered," or autonomous shunt execution. Integrate-don't-replace still applies—extend yard and enterprise systems; do not pitch a rip-and-replace of every MIS tool. See integrate, don't replace.
Shadow the recommendations—proposed shunt plans, suggested dispute packages—before Assist writes anywhere. The trust ladder is identical to sortation: shadow mode before assist.
Safety Tracks Are Not a Chat Feature
Torpedo ladle routes and crossings are hazard zones. Continuous intrusion monitoring from edge CV is valuable. Auto-sirens from a probabilistic detector without human-in-the-loop policy are how you train the plant to ignore alarms—or worse.
Architecture we defend: detections raise an alert with evidence; policy and HITL decide escalation; audit records the chain. Spatial patterns elsewhere in the portfolio (Xenith Spatial) follow the same eyes → twin → approved action loop. Yard safety is not a place to flex full autonomy.
Buyer Questions That Separate Clocks from Chatbots
Use these in vendor reviews for manufacturing and heavy logistics yards:
- Who computes free time—rules or model?
- Can timestamps be edited after insert?
- Show a dispute PDF generated only from sealed events.
- What requires human confirm before execution?
- How are tariffs versioned when commercial terms change?
- What is the connector roadmap beyond the synthetic demo?
If answers 1 or 2 wobble, you do not have demurrage defense. You have a storytelling app beside a radio.
The Outcome Commercial Teams Actually Want
Controllers see rake state without waiting for the next call. Commercial teams export dossiers with evidence instead of reconstructing shifts from memory. Safety officers get intrusion signal without another siloed dashboard. Leadership gets MIS that matches the yard, not the register fiction.
None of that requires the LLM to know the tariff. It requires the clock to be boring, deterministic, and sealed—and the language layer to stay in its lane.
Xenith Yard keeps detention clocks in rules and sensors—LLMs draft dossiers, they do not own demurrage.
Request an architecture brief → · Xenith Yard → · Industrial AI →