A proven release path, and retiring Linux

The design is live

The new visual direction was published through a simpler release path: GitHub source, basic checks, one explicit Cloudflare Git build, then live verification. The four landing pages passed desktop and narrow-screen checks, with no horizontal overflow or browser errors observed. The roadmap remained a future-only table, ordered by score.

This proves that one release worked. It does not prove that the design helps readers more, or that unattended AI publication is ready. Reader benefit remains unmeasured.

Fewer moving parts

Linux previously held the AI runner, isolated publisher, daily health timer and failure-alert hooks. Once the new release path worked, the owner chose to remove those project systems rather than maintain another operating environment.

The first retirement preserved monitoring. The owner then decided a separate daily checker was unnecessary for this project. The remaining project files, services, timer, alert hooks and five dedicated accounts were removed. Two lingering processes under the retired AI account were stopped to complete account removal.

Useful history and the original candidate were preserved in a private Windows archive. Its checksum was verified before Linux file removal. The archive is a historical record, not another active runner. Shared software on the mini PC was left untouched; it has no configured role in this website’s workflow.

The operating model now

1. Prepare a bounded, AI-assisted change in a separate candidate.
2. Build and check the basics, including links and usable pages.
3. Record the source and reasoning in GitHub.
4. Explicitly request a Cloudflare build of the chosen GitHub source.
5. Verify the live pages and retain release evidence.

Linux is no longer required to serve, build or publish the website. There is no daily project health process or project failure-alert service. This removes maintenance overhead but also removes that independent monitoring coverage. Release checks and explicit live verification remain.

AI scheduling and recurring automatic publication remain disabled. The successful release used the then-existing Linux login to request the Cloudflare build; after its removal, a future manual release needs an authorised Cloudflare session. No replacement credential or scheduler was created. Remote provider access grants were not revoked by deleting local files.

Dated architecture snapshot

Candidate → GitHub source and checks → explicit Cloudflare Git build → live verification.

Linux: retired from the project. Windows: private history archive. Recurring AI and publication: disabled.

The current Solution Design can evolve; this record preserves the transition and its trade-offs.

Visual architecture snapshot