The Journal.

Fifty-seven items to Done and four to Won't Do, seven of them belonging to a week already written up and closed in the hours after the last entry was filed — the second week running that the tail after filing has not been empty. A client's domain moved hosts in under an hour on the Sunday afternoon, backup first and verification last. For the junior chess club the week's build was a game viewer: comments and variations, a static-position mode for the teaching pages, keyboard operability, lazy initialisation, and a no-JavaScript fallback that exists as authored because the site has no build step to generate one. A rule cited by seven tickets and reciprocated by none of them was made visible from its own ticket, by a sweep that had been built twice and lost twice before anyone committed it. Two more quality gates were caught reporting the wrong thing rather than nothing at all. A new engagement for a beauty therapy studio went from nothing to a nearly-finished site across two evenings. The trace identifier, the internal developer tool and the family-history foundations stood exactly where they were left.

Fifty-four items to Done — the largest week in this record — and five of them belong to a week already written up, closed in the half-hour after the last entry had been filed. For the junior chess club it was the build week proper: design tokens, a base layout and nine page templates in four days, with the palette's contrast measured against the AA thresholds before a single template was built on it. Then the gates built the week before were themselves audited, and four of the findings were about the checks rather than the site — a version pin that printed but never asserted, an accessibility gate that could not fail on six rules, a required check that gated the deploy but not the merge, and a viewport width nothing measured at all while the automated pass reported green. A second engagement went from signed-off specification to deployable site in a single evening. The retained veterinary practice turned a registration form into a waiting list, the e-commerce items raised a week earlier all closed, and the trace identifier, the internal developer tool and the family-history foundations stood exactly where they were left.

Paperwork first, then platform, then content — twenty-one items to Done, four of them landing on the Sunday evening after last week's entry had already been filed. The junior chess club engagement this journal could not describe a week ago now has both instruments executed: a services agreement and an Article 28 data-processing agreement, signed and returned before a line was built. Then the foundations went in — a private repository whose private status was verified rather than assumed, a static web app in an EU region confirmed in the portal rather than merely intended, and a nine-check consistency gate that notices the things a person eventually won't, including the location data photographs carry out of the camera. Two spikes settled a rendering question on real handsets and a licensing question before it could reach the deliverable. The retained veterinary practice's entries were cleared down again, three new e-commerce items opened on Sunday, and the trace identifier, the internal developer tool and the family-history foundations stood exactly where they were left.

The record, and the work that comes before the work. Seven items to Done and eight closed as Won't Do — a week that decided against rather more than it completed. The practice's own working notes for this site — its conventions, its amendment process, its redaction rules — were moved out of a machine-local store and into the repository, where they can be diffed and argued with like anything else; the check that prompted the move found them six versions out of date. A new unpaid engagement opened midweek and deliberately built nothing, its agreement not yet executed. The long-standing discount-code investigation was closed on the e-commerce side, the retained veterinary practice's form entries were cleared down again, and the internal developer tool, the trace identifier and the family-history foundations all stood exactly where they were left.

The books, and the quiet work of subtraction. Fourteen items to Done across four projects, and not a new feature among them. The practice turned first to its own house — the year-end accounts and the VAT position analysed, the bookkeeping put on an automated footing; then outward, where an enterprise e-commerce order integration lost a layer of logic it had outgrown and gained an honest map of how a partner brand's orders and payments actually reach the finance system. The retained veterinary practice's site had an embedded third-party form taken out and a real booking route put in its place, and a September fee change published well ahead of the day it takes effect. A local dog-training club's handover was settled, and the internal developer tool stood exactly where last week left it.

Proof, and the apparatus of publication. The internal developer tool took thirty of the week's thirty-six closed items — not new faculties this time but the two things that turn a working instrument into a releasable one: a full automated test suite that proves it behaves — unit, property-based, snapshot and component tests, with benchmarks and coverage — which paid for itself at once by surfacing two genuine faults; and the public scaffolding a tool needs before strangers can use it — reference documentation for each cron dialect it speaks, a cookbook of worked examples, and the privacy, security-disclosure and credits apparatus that lets it stand in the open. Alongside it, a family-history application's cloud foundations stayed in flight, and the smaller retained work was quietly kept.

The inward tool, given its working faculties. The internal developer tool took twenty-one of the week's thirty-four closed items, carried from a face to an instrument that does its three jobs: a schedule you can type and read back in plain language, a calendar that shows the days it will actually fire — month, week and agenda, exportable to a real diary or spreadsheet — and a compare mode that sets two schedules side by side and marks the difference. Alongside it, a clinical canine massage practice's site gained its audit, telemetry and bot-protection layer ahead of launch, and the smaller retained work was quietly kept.

The inward week, continued — and the inward thing given a face. The new internal developer tool took thirteen of the week's eighteen closed items, carried from a working core to the surface a person actually touches: a visual design system and layout shell, working state held in a shareable link, and an end-to-end test harness wired into CI. Alongside it, a clinical canine massage practice's contact pipeline was proven and switched live, and the smaller retained work was quietly kept.

A week turned inward. A new internal developer tool — a cron-expression calculator, describer and comparer — took the bulk of it: thirty-two items, from an empty repository and CI pipeline through a complete domain layer and three cron parsers to a working set of services, while the enterprise e-commerce support carried on and the retained clients were quietly kept.

The mirror image of last week. The new clinical canine massage practice took the bulk of it — thirty-seven items, from signed paperwork through a scaffolded repository and provisioned cloud to a working, tested contact pipeline — while the internal platform's modelling advanced and the retained clients were quietly kept.

A building week, and mostly out of sight. The internal quantitative sports-analytics platform took the bulk of it — twenty-six items, from data ingestion through modelling to a working execution service — while a new client engagement's foundations were laid and the retained clients quietly tended.

Closing week. The company-website infrastructure programme reached its formal end — DNS authority returned to GoDaddy, legacy hosting cancelled, observation closed — while a new local-client engagement began the right way, with foundations before code.

The week after. Phase 7 closed as an epic, telemetry sharpened, uptime watched from the outside, mirrors and archives put in place — and an enterprise e-commerce go-live entered its post-cutover hyper-care phase.

Launch week. Two production go-lives in seven days — the new company website went live at thecodeabides.co.uk, and an enterprise e-commerce platform reached its own cutover milestone alongside.

Two long-running engineering arcs converging in the same seven days — a new company website on Azure built feature-complete, and an enterprise e-commerce client cutover commenced. Forty-nine items to Done across three projects.

A quieter week, by design. The headline activity was unglamorous and important — a comprehensive npm package upgrade sweep across five Node.js microservices, kept on cadence as a matter of supply-chain hygiene.

Five active projects, including the kick-off of a new internal initiative — a quantitative sports analytics platform moved from idea to scaffolded codebase, with progress alongside on greenfield development, enterprise e-commerce, and client IT.

A founding week. The full application scaffold for a bespoke web platform came together on a .NET 10 / C# 14 stack with Onion Architecture across five projects, and the CI pipeline that will carry the work was wired up alongside.