Recall Trail
A repair volunteer receives a recall for a batch of replacement parts. One of those parts is still in service, but it was moved from its original toolkit into a different assembly. The volunteer needs to find the kit that now contains it and the checkout record for that kit.
Recall Trail stores batches, individual parts, assemblies, kits and loans in an embedded Relate database. Starting from the batch ID, a Cypher query follows active installation links through the assembly and into the current kit. The result shows the path and its active loan record. A removed installation and a returned loan stay in the database as history.
The local sample follows a single part from LOT-7 through HEAD-2 into KIT-02, which is checked out on LOAN-9. Reopening the database preserves that result. The sample records are fictional and can be recreated from the source. A repair team would need to record part IDs at installation and update the links whenever a part moves.
I used Codex to implement and test the Python workflow and prepare the demo. Recall Trail runs Qwen3.5-4B locally through LM Studio to identify the batch in the question and call the lookup tool. Relate 1.0.0 follows active inventory links with a parameterized Cypher query through a read-only connection.
Built With
- python
- relate
