the evolving website
04 / Behind the website

Solution Design

Understand how the website works,
and how it changes over time.

GitHub holds the source and checks. Cloudflare builds and serves explicitly requested releases. Linux has been retired from this project. A finite one-week AI-assisted publishing trial is enabled; Cloudflare automatic deployment triggers remain disabled.

A place for each kind of question

How this website is organised. Each page has one main purpose.

A place for each reader question. Proposed design · 18 October 2026. Text description and links follow.
Proposed design · 18 October 2026

Page navigation, not a publishing pipeline.

Diagram description and links

The homepage connects readers to these page destinations.

Current architecture · one-week trial

  • Windows must be awake with the app running.
  • Trial slots: 5 am, 11 am, 5 pm and 11 pm, fixed GMT+10.
  • First run: 18 October 2026, 5 pm. Last: 25 October, 11 am.
  • Hard stop: 25 October, 1:45 pm GMT+10. Review before extending.
  • Owner ideas and research share one roadmap. Each run assesses up to 20 ideas and selects a justified batch with no fixed item limit.
A finite AI improvement loop. Trial enabled · 18–25 October 2026. Text description and links follow.
Trial enabled · 18–25 October 2026

Windows awake + app open. Linux retired. Reader benefit unmeasured.

Diagram description and links

Arrows show the order of the release flow. The dashed return arrow represents saved outcomes informing the next decision; it is not a separate automatic deployment trigger.

From an idea to a useful change

The owner has authorised scheduled AI releases for the one-week trial. Each run can select, implement and publish changes without a separate owner approval. GitHub checks, a requested Cloudflare Git build and live verification form the release path.

  1. Identify a reader needUse feedback, research and previous outcomes. No change is valid.
  2. Prepare a changeAI assists with the design and implementation in a separate candidate.
  3. Check the basicsBuild the site, check links and inspect usable pages.
  4. Keep the sourceGitHub records the change and its reasoning.
  5. Request the buildThe AI task requests a Cloudflare Git build of the merged source. Cloudflare's automatic Git triggers stay disabled.
  6. Verify and learnCheck the live pages, then assess the reader outcome when evidence is available.
What is running today?
  • Cloudflare builds requested GitHub releases and serves the website.
  • The finite AI trial runs on Windows.
  • Linux project processes, daily monitoring and alerts are retired.
  • History and the original candidate are preserved in a private Windows archive.
  • Cloudflare automatic deployment triggers stay disabled.

Tools with a clear job

Tool / serviceWhy it is hereCurrent state
ChatGPT scheduled taskAssesses ideas, implements selected changes and requests releases.Owner-authorised trial on Windows; no approval needed for each release. PC awake and app open.
AstroTurns content and designs into static pages.Existing production framework.
Cloudflare PagesBuilds and hosts the public website.The AI task requests each Git build; automatic Git deployment triggers stay disabled.
GitHubKeeps source history and checks proposed changes.Authoritative source, with basic page checks and secret scanning.
Git + saved run receiptsPreserves versions and evidence.Existing records retained.
Sites local design workflowHelped develop and review the visual direction.Design workflow; this website is not hosted as a ChatGPT Site.
Shared health checkerChecks that readers can open and use pages.Release checks and explicit live verification; no daily Linux process.
ntfyPreviously delivered project failure notifications.Project alert hooks removed. Shared package/server left untouched, outside this project.
Linux mini-PC + systemdPreviously ran the AI runner, publisher and health timer.Retired: project files, services and five dedicated accounts removed. History archived on Windows.

Architecture has a history, too

Changes to tools, services or data flows update this page and add a dated SVG to the journal. Earlier snapshots stay unchanged.

18 October 2026 · One-week trial →

18 October 2026 · A proven release path and Linux retirement →

How we will measure reader benefit

Future reader-benefit plan; no reader-task study has been completed. The last live audit found a Cloudflare analytics beacon. That is separate from measuring comprehension or usefulness. Ask willing readers to find the newest published update, explain what changed and why, and find the next proposed improvement. Record completion, confusion and optional usefulness feedback.

Establish a baseline, repeat the tasks after relevant changes, and use findings to keep, revise or reverse the change. Small samples provide directional evidence. Traffic, visual polish and technical checks do not establish reader benefit.

Begin with a small manual feedback record. Reader benefit remains unmeasured until evidence is collected.