0 of 3 lessons complete
Trace Fundamentals
Kanoa Trace is built on four objects:
| Object | What it is | Example |
|---|---|---|
| Lot operation | A configured type of operation | Transfer, Machine, Ship |
| Lot operation event | One time an operation was carried out; groups its inputs and outputs | Transferring 100 lbs to Machine 1 at 9:05 |
| Lot | The identity of a quantity of material: just an ID, a name, an item and a unit | RAL0000001, AL2024, lbs |
| Lot event | A lot taking part in an operation event as an input or an output, with a quantity, asset, state and time | Input: 100 lbs of RAL0000001 at Receiving |
A lot doesn't store its quantity, location or state. When Lot Manager shows "RAL0000001, 900 lbs, Receiving, OK", it's adding up that lot's events. Current inventory is a view of the event history, which is also what makes tracing possible.
Inputs remove material from somewhere; outputs add it somewhere. That covers every pattern you'll build:
| Pattern | Inputs → outputs | Example |
|---|---|---|
| Transfer | A lot → the same lot at a new location | Receiving → Machine 1 |
| Transformation | One or more lots → a new lot | Aluminum → machined pins |
| Multi-input | Several lots → one lot | Two ingredients → one blend |
| Split | One lot → several lots | Inspected parts → passed and scrap |
A backward trace follows outputs back to their inputs ("what went into this package?"). A forward trace follows inputs to their outputs ("where did this aluminum go?").
In this section you will:
- Configure the lot operations, lot naming and storage locations the CoreForge flow needs.
- Run the complete flow by hand in Lot Manager, from receiving to shipping.
- Check inventory and run backward and forward traces.


