Systems, built to prove themselves.
I write the spec before I write the code. Then: pipelines that watch hours of footage and cite the exact second of every claim, memory that never rewrites its own history, and experiments that run, score, and improve themselves every night. Every claim ships with a receipt.
Three systems, each with receipts. Every number below traces to a real artifact.
Evidence-cited narrative compiler
Watches hour-long videos, extracts timestamped claims, and compiles visual storyboards where every factual beat cites the exact second it was said. Built so it cannot state what it cannot cite.
Private repository; walkthrough on request.
Bi-temporal memory
Memory that never erases. Facts are invalidated, not deleted, so the system can be asked what it believed at any point in its history.
Private repository; walkthrough on request.
Self-improving animation organism
A machine that studies motion by night. Experiments are generated, scored by its own vision organ, and only the winners ratchet forward into the next run.
The systems underneath
Smaller tools that keep the machine honest: keyboard-lighting control for hardware the stock tools do not recognise, wallpaper and theme automation on KDE, and the single-writer daemons that stop two processes fighting over one device.
The rules every system is held to, written before the work rather than after it.
Ownership contracts, isolation boundaries, and control-plane designs get written, dated, and reviewed before anything is built. More work at the start; fewer mistakes later.
Isolation, control-plane, and orchestration specs on file, 2026-08
Concurrency gets a lease, not a hope. A single writer per path — across multi-agent workspaces and down to the lighting stack on this laptop — enforced by architecture, not discipline.
Workspace write-lease contract, 2026-08-09
Every material action runs inspect → checkpoint → change → real probe → receipt. If a probe was not possible, the result is UNTESTED — never PASS.
Receipt pipeline from the workspace contract, 2026-08-09
Every failed run records a failure receipt: exit code, output, timestamp. Behind it sits a checkpoint that can be restored, so nothing disappears quietly and nothing is retried blind.
Orchestration spec: failure receipts and rollback, 2026-08
I came to Salford to study entrepreneurship and innovation, and found the systems behind the ideas more interesting than the pitches. So I learned to build them by shipping, breaking, and measuring: pipelines, memory, experiments. The habit became nightly work, and the nightly work became the systems above.
I answer everything. Walkthroughs of the private repositories are available on request.