Product
A model of the operation that says what it knows.
Three parts. The floor twin runs today. The gate model is in design. The agent network has a working reference hub and a phone inbox on the way.
The floor twin
A production area is rebuilt from one walkthrough video. No survey, no CAD file requested. Every machine on the floor carries the frame it was seen in, so a question about the model can be answered by looking at the footage.
Material moves between stations along routes with finite queues and carrier handoffs. Stock, receiving capacity and machine eligibility govern the flow. A stoppage propagates into queues, throughput and elapsed order time, and the production ledger shows working, idle, blocked and fault time.
Repairs compete with production for crews, skills, shifts and spare stock. Activity, energy and modelled cost are traced by resource, product, order, material and lot. Two scenarios can be pinned and compared at the same simulation time.
Exists today
- An illustrative 3D layout, video-relative rather than surveyed
- Simulated resource states and material flow, labelled as simulated
- Section summaries, heat-map filters and scenario comparison
- A production ledger, a repair model and per-lot cost tracing
Pilot work
- Connecting your cameras, scanners and buttons
- Event definitions for your manual workstations
- Order and BOM linkage, one read-only feed
- Site recognition that is stable on your floor, measured against your footage
The gate and logistics model
In design this week. Vehicles, visits, docks, shipments, loads, receipts and an append-only gate log, joined to the same orders and stock the floor twin already carries.
It answers the questions a plant owner asks about the edge of the building: which trucks are waiting at the gate now and for how long, which docks are occupied, what left the building today and against which order, and whether anything was received against a withdrawn revision. Every field says whether a sensor, a person or a document observed it.
Status on 2026-09-16: design document in progress, first coded slice with tests to follow. Not yet part of the demo.
The factory agent network
One wire for the things a customer and a factory say to each other: capability, request for quote, quote, order, change notice with revision, shipment, gate crossing, receipt, nonconformance, invoice. Each message is signed by the sender, numbered, and kept in an append-only journal both sides can read. There is no version of an order that only one side has.
The refusals are the product. A quote missing price, currency, lead time or validity is refused. An order must name the quote it accepts, carry the same price, and arrive before the quote expires. A change acknowledgement must state what was already committed, because that sentence is the money.
Where it stands
- Protocol, signed envelope and reference hub built, 48 checks passing on 2026-09-16
- Signed HTTP delivery and the journal work today for software that can POST
- The phone inbox for a factory with no software is this week's work
- Node-to-node transport has a fixed schema and no implementation yet
Bring one late order. We show you where it waited.
Thirty minutes on a call, then a walk of one area of your floor with the twin on a laptop. No preparation needed.