---
title: "Wrenchloft: maintenance work orders for a manufacturing plant"
author: "@chris"
author_url: https://elements.dev/u/chris
published: 2026-10-07T01:39:23.953Z
url: https://elements.dev/demos/01a11403-eb60-7a31-9200-27c9491b2bbc
kind: post
format: article
---

# Wrenchloft: maintenance work orders for a manufacturing plant

by [@chris](https://elements.dev/u/chris) · 2026-10-07

## Description

Work orders on a live status board, preventive schedules that open jobs when due, phone timers for technicians, parts stock with a reorder list and a downtime dashboard.

Wrenchloft needed three kinds of accounts, a board and technician timers that update on every screen, stock that drops as parts are used, and preventive work that opens itself on schedule. Each of those is a part of Elements, so the agent spent its 23 minutes on the maintenance shop itself.

**What Elements gave the app**

- **A live board and timers.** Work orders, notes, photos, part uses and parts are LiveTables. A manager drags a card to On hold and the technician's phone shows it at once; a technician presses Start and the card on the manager's board starts its clock.
- **Stock that stays right.** Using a part is an `@rpc` call that locks the part's row, lowers its stock and records the use in one transaction, so the count stays exact when two technicians reach for the same part. The parts page and its reorder list update as the count changes.
- **Preventive work on a schedule.** A one-line cron schedule runs a job every 15 minutes that opens a work order a week before each schedule comes due, then rolls the schedule forward.
- **Photos from the floor.** Technicians and requesters attach photos straight from a phone camera through a server call, stored in Postgres and served by the app's own route.
- **Roles and sessions.** One guard on the signed-in user's role sends managers, technicians and requesters to their own pages and keeps every server call to the right people.
- **Data from SQL files.** Migrations define the plant and seed six accounts, twelve assets across two buildings, nine preventive schedules, fourteen parts and thirty-six work orders with their parts and notes. The project server applied each one as soon as it was saved.

**What the project server gave the agent**

The project server runs alongside the agent and answers as soon as a file is saved: it type-checks the templates, TypeScript and SQL, applies migrations and reruns the tests, so every question came back right away and the agent kept building.

**What shipped**

The app type-checks with zero errors and all 46 tests pass. Every page works on desktop and phone, and live updates arrive across tabs, such as a card moving on the board, a timer starting and a stock count dropping.