Closing weeks are quieter than their predecessors, but no less weighted. The infrastructure programme that took the company website from a brief through architecture, build, launch, and post-launch reached its formal end this week — DNS authority returned to its proper home at GoDaddy, the legacy IONOS hosting cancelled, the seven-day observation window closed without incident. And on the other side of the desk, an entirely new local-client engagement opened the way new engagements ought to: legal foundations being drafted, the spec read with care, the repository created with branch protection before a single line of code.
The headline close-out was the formal end of Phase 8. The seven-day live observation window closed on Wednesday with the site holding up cleanly under real traffic — uptime monitors green throughout, the contact form receiving and dispatching, no critical issues outstanding. With that confirmation in hand, the long-deferred registrar/DNS-host realignment was actioned: DNS authority for thecodeabides.co.uk had been delegated from GoDaddy (where the registration lives) to IONOS (where the legacy WordPress site was hosted) since the project began — an artefact of the legacy hosting arrangement, not a deliberate posture. With the IONOS-side cutover long since complete, the nameservers were flipped back to GoDaddy where the registration sits. Purely operational — no data-flow change, no application change, no compliance impact — but structurally important: registration and DNS authority now properly aligned at a single provider. The §16 Phase 7 nameserver-migration step that AMD-021 formally added to the spec on 10 May executed cleanly. And then, DNS authority safely relocated, the IONOS managed WordPress hosting was at last cancelled. Confirmation email received. The legacy estate is gone.
Opening alongside, and characteristically at the other end of the discipline, was a brand-new local engagement — a clinical canine massage practice in the Severn valley, with a spec already at v1.0 and the contractual position to be put in place before any code is written. The repository was created in the company GitHub organisation with branch protection configured per spec §14.6.3: pull-request-required merges on main, status checks required, force pushes and deletions disallowed, the .gitignore covering Node, .NET, IDE files, and local.settings.json. A draft of the services + processor + Domain Hosting Schedule agreement is in progress alongside — a single plain-English document covering services scope, UK GDPR Article 28(3) processor obligations (documented instructions only, confidentiality, technical and organisational measures, subprocessor authorisation, DSAR and breach assistance, return-or-delete at end), and a Domain Hosting Schedule recording that the domain is held under the company's IONOS account with explicit transfer-out terms on termination. A one-pager-plus-schedules format, appropriate for an SME engagement; not an MSA. The final four [TBC] items from the spec — the vet consent form, the WhatsApp publication decision, the information architecture confirmation, and the terms-and-cancellation content — are with the client for resolution in a single batched email. Foundations before code; the sequencing is deliberate.
— On endings and beginnings —A long programme closed properly, and a new engagement begun with proper foundations — the same discipline, applied to both ends of the same week.
On the enterprise side, the post-go-live hyper-care phase continued at its now-familiar tempo. Five investigations and operational supports landed across the week — a procure-to-pay investigation into a missing NetSuite order, an investigation into missing fulfilment line items, an investigation into multiple-shipment ordering behaviour, P2P transfer-ordering support, and bin warehouse transfer support. The procure-to-pay and warehouse-transfer flows are where live volume meets edge cases, and each of these was the kind of small, specific item that only emerges under real load. Individually unremarkable; collectively the unglamorous follow-through that distinguishes a settling cutover from a problematic one. The platform continues its slow movement from hyper-care toward steady-state.
For the retained Malvern Hills Veterinary Practice, a quietly substantive four-item week of practical IT stewardship: PC updates rolled out across the practice, scanning software installed on the two front-desk machines, a web-form data cleanup pass completed, and a face-to-face with one of the partners. The kind of low-frequency, hands-on operational care that keeps a small clinical practice running — the analogue cousin of software stewardship, attended to with the same disposition.
Looking ahead, the company-website chapter now properly passes into ordinary operations: a stable system on Azure, external uptime watch in place, an off-GitHub mirror running nightly, the monthly submission-audit ritual queued for its first run at month-end. The Severn engagement proceeds to its Phase 2 once the signed agreement is in counterpart and the [TBC] content is back from the client. The enterprise hyper-care continues its gradual taper. And the older WordPress journal backlog continues its progressive re-publication, three to five entries a week, the new editorial voice applied as each lands.
Thirteen items to Done. Two more in progress. A long programme closed properly. A new one begun the right way. Two retained clients tended. The deliberate, unhurried practice — between.