This is the first monthly entry. On 13 October the journal moved from a weekly account to a monthly one, and the job the weekly entries had been half doing, showing someone outside what the work actually looks like, went to a new Work section. Eight case studies went up on the 13th and 14th: three of our own products and five client sites, each written once the work had settled, from what it does now rather than from how it got there.
A study names the client, as the homepage roster always has, and the journal still does not, so the same work can now be read in two places under two sets of rules. That is deliberate. The journal is the inward record, written while things are moving. A study is written once and read by the very people it describes, so the test for every sentence was whether the client would be glad to see it published. Before a word was drafted, each client's executed agreement was read for anything that would stand in the way, and anything commercial stays out as a matter of course. The roster itself now reads in two columns, the larger engagements in one and the local practices in the other, and a local row links to its study where there is one. The larger names will stay as credits, and one more study waits for its engagement to finish. Among the three products is N17 Time's sibling, unnamed in the last two entries, which now has its name in public: HR4 Time, at hr4time.app, an unofficial fixtures page for Hereford FC of the National League North. Its sources stay unnamed here, as N17 Time's always have.
— On case studies —The journal is written while things are moving. A study is written once, and read by the people it describes.
A local dog-training club's new site went live on its own domain on 21 October. All twenty-three records in the old zone were accounted for in a written plan, each with its treatment and a way back, and copied across exactly, so the new zone could be proved to match before anything moved. A test message made the round trip while the change propagated and again once it had, passing every authentication check both times. The old www address now redirects to the bare domain with its path and query intact, both forms were sent end to end and arrived where each is meant to, and the site sets no cookies and has nothing added to its pages in transit. Its form endpoints answer anything that is not a form submission with a plain refusal and a sentence explaining it, rather than an error. There were no mail incidents. Earlier in the month the club's class descriptions were replaced, word for word, by a trainer's own rewrite, which the trainer signed off before launch.
The retained veterinary practice is registering new clients again. The change had been specified in advance and parked until the practice was ready, and when it was, on 20 October, it shipped the same day. The registration page went back to the address it had on the old site, the waiting-list address now redirects to it, and every applicant receives an acknowledgement by email, in fixed wording, sent in the practice's name with replies going to the practice. A test registration from a phone produced both messages, and the practice was told the same day.
Five client sites now revalidate their stylesheets and scripts on every visit. The edge in front of each was set on 25 October to respect the site's own caching headers rather than a default of its own, so a deploy is visible on the next page view, at the price of one small not-modified reply per file. Photographs are the opposite case. On an independent garage's site, where two new ones went up that morning, images are kept for a year, so a changed photograph arrives under a new filename instead of waiting for a cache to forget the old one, and the site's check script now confirms the caching rule among its twenty-two checks. Earlier in the month a beauty therapy studio's contact form began weighing how long a message took to write and how many links it carries: one or two links earn a flag in the subject line, more than that and the message goes nowhere. The studio's mail policy moved to enforcement in the same change.
The month's largest workstream was a new internal product, not yet named here: a site that works out, after each round of a motor-racing championship, who can still win it, what the leader needs at the next race to settle it, and the earliest round at which that could happen. It was begun on 15 October and was serving from its own domain on the 18th, thirty-four items in five days. Every sentence it shows is generated from the season's data, so none can go stale, and a test holds each headline to thirty-five words or fewer. The data refreshes itself on race weekends and commits the result back to the repository, which shaped two decisions. The repository's protection blocks force-pushes and deletion but not direct pushes, because the refresh could not otherwise commit, and the deploy runs only once the checks have passed, so a broken push cannot reach the site. And a refresh whose race results have run ahead of the source's own standings is refused, keeping the last good snapshot rather than publishing a table that disagrees with its own results. The site uses no one else's marks, logos or photographs, says on every page that it is independent, and has a written procedure for taking anything down first should a rights holder ask.
The family-history web application changed shape on 28 October. Its original plan had a database, an API and an admin area with its own sign-in, at an estimated sixteen to twenty pounds a month in hosting, all for a site with one author. It is now a static site built from content kept in its repository: an event or a photograph is a file checked against a schema when the site builds, and publishing is a merged pull request. Write access is repository access, the public site is read-only by construction, and the running cost falls to the price of a domain once it has one. Six stories closed as superseded that morning, and the features followed within three days: a timeline; a map that joins the places in date order and can play the route stop by stop, or step through it when motion is reduced; a gallery whose images load only on the site's own pages, with right-clicking left alone by design; and an album viewer that publishes a page only once every photograph on it has been verified. The scanned originals never enter the site. They are inventoried with checksums, the script that moves them copies without ever overwriting or deleting, and a research standard written alongside requires every claim to cite a source or to say plainly that it rests on family knowledge.
The company site's own functions moved to .NET 10 on 23 October, eighteen days before the platform ends support for .NET 8. Only the target framework, one package and a line of configuration changed. The health check and the security-report endpoint were verified within minutes of the merge, and the contact form, the one path that needs secrets the development machine does not hold, was confirmed shortly afterwards by a real message arriving. The local tooling and the deploy workflow moved to their Node 24 releases the same evening, which retired a deprecation warning every deploy had carried since late September. Both changes were recorded in the specification by amendment that evening, and it now stands at version 1.27.
Most of October came down to writing things once, at the point where they will stay true. A study waits until its engagement has settled. A product's sentences come from its data, so they cannot drift away from it. A stylesheet is checked on every visit rather than trusted for a while. And the journal, from this entry, waits for a month to settle before it says what happened in it.