tas_ixa

A clock device on a wall produces tab-separated exports and no opinions. This turns them into per-employee hour reports, and handles the part the device cannot: the day somebody forgot to clock out.

The design rule is the one I learned on validated machines — history is not edited, it is corrected. A correction is a proposal until it is approved, the original reading stays where it was, and every applied change can be undone from a history panel. An incomplete session shows its running duration instead of the word "incomplete", because a supervisor needs the number, not the label.

It started as a Python script that parsed the export files, grew a web UI, and became difficult to reason about — one server file doing everything. Splitting it into readable chunks helped, but only postponed the decision.

May — the rewrite. Migrated to a TypeScript monorepo with Vue and Vite, which is where the approval workflow, the change history with undo, and multi-file uploads landed. Then a deliberate pass removing dead code and the antipatterns the first version had accumulated.

August — the foundations. Login and session handling hardened against leaking personal data, an architecture document written to make the module boundaries explicit, and persistence moving from flat files to embedded SQLite — in progress: that last migration still has red tests, and it is the next thing to close.