Build Log
What shipped, when, and what broke. Dated notes from live builds, not plans and not intentions.
The link had no image at all
A shared link to this site unfurled with nothing. Two separate faults producing one symptom, and only one of them was the thing it looked like.
The build log now drafts itself, and still waits to be asked
This entry exists because it is the thing it describes.
Ten pages at 100, and one real failure
Every page on this site scores 100 for accessibility on Google's own hardware. The audit found exactly one genuine failure, and the score is still not a conformance claim.
Eleven days of green, and the thing it was protecting died anyway
A scheduled job returned 200 every day for eleven days while completely failing its purpose, and an error path meant to be safe was losing enquiries. Two checks that reported success.
A deployment that was never built from the remote
A merged pull request published nothing on a client site for three weeks. The project was wired to git correctly the whole time, and the diagnosis that said otherwise was wrong.
The name was taken, and we kept it anyway
A clearance search found an active company and a live consumer brand on the same name. Here is the reasoning for taking it regardless, and what changes as a result.
Brands as configuration
A content engine that runs any number of brands from one codebase, where a brand is a config file and a voice guide, and the controls that stop it publishing the wrong thing are enforced in code.
Three days, and the slow part was photography
A clinic site built brief to live in three days across thirty commits, around the booking system the clinic already used, with every account created in the owner's name from day one.
Sensing and control belong in one app
Traffic monitoring and paid-spend control across an estate of sites, built as one application over one schema rather than two dashboards that disagree.
Who you may lawfully contact is a data problem
A public site with a gated deal room, and two counterparty databases behind it. Both carry a certify-before-outreach gate, because in this business the question is not only who you want to contact.
A deal pipeline across two markets
Property acquisition and disposition for HW Legacy Group across the UK and the US, where the same pipeline has to behave differently depending on which side of the Atlantic the asset sits.
Built, and deliberately not published
A corporate site for a Queensland high-voltage contractor, finished in ten days and then held with the DNS unpointed, because the licence its claims depend on had not landed.
Seven stages, one pipeline
Fathom Money senses demand, writes the product, gates its own quality, publishes, sells, and unlists itself if refunds spike. Built to test whether a business can run without a human earning attention by hand.
An English window onto a foreign registry
A private working application over the Georgian cadastre for Georgian Land Limited, separate from the public site and permanently behind its own sign-in.
One database, many shops
Chairhouse is a booking and loyalty product for barbershops. The hard part was never booking. It was making one database serve many shops without any shop ever seeing another's data.
A marketing site that grew a backend
Georgian Land Limited needed one document to reach a narrow audience and nobody else. The interesting part is that a gate which hides content in the browser is not a gate.
Where this started, and who it was for
The first build was an investment platform and its back office for HW Legacy Group, in March 2025. There was no brand and no offer, just a job that needed doing.