A new design and a simpler publishing workflow

Design and structure

• Replaced browser-default styling with shared typography, spacing, colour and navigation.
• Kept the manifesto on Home. Added a future-only ranked Roadmap and a Solution Design page.
• Grouped early journal records while keeping their original addresses and text.
• Added metadata, structured data, a sitemap and crawler access guidance.

Homepage comparison · 16–18 October 2026

Publishing and Linux retirement

• Proved the GitHub → Cloudflare Pages release path with basic checks and live verification.
• Removed the project’s Linux runner, publisher, daily monitoring, alert hooks and dedicated accounts.
• Preserved useful history and the original candidate in a private Windows archive.

Reader navigation

• Added section links to longer articles and links to earlier project context.
• Build, link and browser checks passed for the published changes. Reader benefit remains unmeasured.
• The navigation record keeps the original reasoning and limitations.

One-week AI trial

• A scheduled activation completed a production release. Later owner-triggered rehearsals published the trial explanation, diagrams and corrected homepage wording.
• Enabled scheduled AI work at 5 am, 11 am, 5 pm and 11 pm fixed GMT+10, from 18–25 October 2026.
• Windows must be awake with the app running. Each run can assess up to 20 ideas and publish its recommended eligible batch without separate approval for every release.
• First recurring slot: 18 October, 5 pm. Last: 25 October, 11 am. Hard stop: 25 October, 1:45 pm GMT+10. Review before extending.
• Cloudflare automatic Git deployment triggers stay disabled. The AI task requests each build.
• Kept one shared roadmap and left Linear out. Consolidated Notion into a short current hub and historical archives.

Writing style and visual references

• Applied the owner’s writing style across current pages, labels and daily summaries.
• Shortened repeated explanations and used direct dot points.
• Kept the manifesto headline, facts and original historical article bodies.
• Added image descriptions and discovery metadata. These help readers and crawlers; they do not guarantee indexing or AI citations.

What we will assess

• Useful changes, no-change decisions, failures, costs where recorded and owner effort.
• Whether readers can find updates, explain changes and identify what comes next.
• Use saved records and feedback to improve decisions; the AI model is not training itself.

Search and run reporting

• Added keyword search for page summaries and journal text, with links to the source pages.
• Matching happens in the browser. No new search service, API key or query log; AI-generated answers remain future work.
• Added a policy requirement to report each run’s changes, publication, live verification and any manual intervention. Removed the separate review schedule.
• Trial timings stay unchanged. Reader benefit from search has not been measured.

Search results with context

• Added matching source excerpts and dates to search results, so readers can see why a journal entry matched before opening it.
• Labelled daily entries and original records separately. Historical text stays unchanged.
• Search now reads future idea titles and descriptions from the shared roadmap. The roadmap no longer lists completed keyword search as future work; AI answers remain proposed.
• The existing browser search and release flow stay the same. Reader benefit has not been measured.