AI answers with source links

Ask this website

• Added an explicit Ask AI action on Search, using Cloudflare Workers AI.

• The owner authorised the AI binding. The account remains on Workers Free; no paid plan or overages were enabled.

• A Pages Function selects public source excerpts, requests one short answer and returns source links. Current pages take priority over dated history.

• Choosing Ask AI sends the question and selected public text to Cloudflare. Keyword search stays local. No query database or vector store was added.

Keep it useful

• Added short FAQs about scope, checking sources and unavailable AI. Kept the Search page and its navigation link; a global search box can wait for evidence that readers need it.

• Limited question size, output and waiting time. Invalid citations, missing sources or unavailable AI lead back to source pages or keyword search.

• Removed the completed AI-answer idea from the future roadmap. Reader benefit still needs a willing-reader baseline; AI output is not proof of improvement.

The release workflow and one-week trial timings are unchanged. Earlier journal records and diagrams remain preserved.

Public disclosure review

• Reviewed the journal, Solution Design, public capture metadata and linked screenshots for sensitive operational information.

• Kept the architecture and decision history public. No credentials were identified in the reviewed public materials; this is not a guarantee that the system has no vulnerabilities.

• Added a clear disclosure rule: credentials, private network details, raw operational logs and recovery archives stay private. Existing dated records remain intact.

• The AI endpoint validates requests, reads only site-owned public sources and renders plain text. It has no publishing credentials, command execution or arbitrary browsing tools.

• Added response headers to prevent framing, block embedded objects and deny unused camera, microphone and location permissions.

• Removed the retired health-checker entry from current Solution Design. Linux has no role in the website; its dated retirement records remain in the journal.

Reader feedback and discovery

• Reused the existing Cloudflare Analytics integration. Added optional Yes / No usefulness feedback without a survey service or login.

• Daily page counts live in a small Cloudflare D1 table. No names, comments or visitor IDs are saved. Aggregate reports cover 90 days; older rows are removed on the next submission.

• Prepared search-provider verification. Search reporting becomes useful only after verification and enough data; bot access is not proof of indexing or citations.

• Future runs review available evidence, report sample sizes and uncertainty, and reconsider the existing roadmap. Traffic and voluntary votes alone do not prove reader benefit.

• The one-week trial schedule is unchanged.

19 October 2026: optional feedback becomes daily D1 counts. Cloudflare Analytics measures reach and performance; verified Google and Bing reports provide discovery signals. Available evidence informs roadmap priorities and the existing release. Missing data is reported; no new review schedule.

Scan activity and plan your reading

• Added a compact activity chart to the journal index. It compares topics in the latest seven daily entries and links to each day. Counts describe the written record, not releases or reader benefit.

• Added approximate reading times near the top of longer journal articles and Solution Design. The estimate uses 200 words per minute, includes expandable notes and excludes navigation and feedback. Diagrams may take longer.

• Kept the chart in HTML and CSS, with text counts and keyboard links. No chart library, new service or tracking event.

• Google ownership is verified and its sitemap was submitted. Bing ownership is verified; two sitemap submission attempts returned a provider server error. Search reports are still processing.

• Put the journal activity chart in newest-first order, matching the entry list. The current policy applies this to future date-based lists on the journal landing page.

• Captured the owner’s proposal for a daily manifesto growth-ring visual on the future roadmap; it is not implemented.

• Added a plain-text sitemap fallback, generated from the same page list as the XML sitemap. The XML image entries remain intact. Provider acceptance is checked after publication; file availability alone does not prove indexing.

Homepage activity and clearer entry points

• Replaced the static homepage orbit with four rings for Home, Journal, Roadmap and Solution Design. Each ring has seven fixed daily segments, ending on the latest journal date.
• The daily journal supplies the activity data. Each date counts once per section; routine release logging does not count as a Journal improvement. Missing historical records stay unknown. Activity does not measure reader benefit.
• Added one shared list of source records, readable counts and keyboard access. No chart library, chart JavaScript or separate activity ledger.
• Added an Ask AI link to the existing Search form and three short diagrams explaining saved records, publishing and the planned reader study. No question is sent merely by opening Home.
• Removed the completed homepage visual from the future roadmap. The one-week trial timings and publishing workflow are unchanged.

Clearer homepage choices

• Replaced the text-heavy introduction with three visual links: Ask AI, Journal and Roadmap. Ask AI opens the existing Search form; it does not send a question automatically.
• Aligned the action cards with the activity panel. Ranked rings and labels by active days, with the busiest section outside. Section colours stay consistent; ties keep a stable order.
• Moved counting detail behind one disclosure and removed the repeated homepage activity list. The journal remains the source.
• Shortened the explanation to Learn, Change, Check. Kept the model-training clarification, trial dates and honest reader-benefit status. No new service, tracker or chart library.
• The one-week trial schedule is unchanged.

Ask AI without leaving the homepage

• Ask AI now expands a question field on Home. Two suggestions cover the manifesto and the highest-ranked future idea. The roadmap suggestion refreshes with the website build.
• Choosing a suggestion fills the field. Only Ask sends the question. Answers appear beneath the form with numbered source links; Search remains the fallback.
• Reused the existing Cloudflare answer service and limits. Added consistent outline icons to the homepage actions and Yes / No feedback. No new service, query store or schedule.
• A single-line field aligns with Ask. Two compact suggestions sit beneath it, and a green border separates the answer from the form. Source retrieval preserves journal paragraphs and respects dates and quoted section titles in questions.
• The one-week trial timings are unchanged. Reader benefit remains unmeasured.

More future ideas

• Expanded the future roadmap from five to fourteen ideas, ranked by priority. Added eight researched proposals and a dated statistics-page proposal.
• Broadened affiliate-link research to commercialisation options, including useful paid resources, services and sponsorship. No commercial feature is active.
• Updated the search proposal to reflect homepage Ask AI. These remain future ideas, not delivered features or measured benefits.
• Kept one roadmap and the existing trial schedule. No new service or scheduling system.

What changed our mind

The roadmap is one example of a revised decision, not proof that the site has become more useful.

1. Earlier approach: the 17 October roadmap proposal organised past, present and future work together. Its expected benefit was an editorial hypothesis.
2. Evidence: the 18 October design record separates future ideas from completed work and records positive owner feedback about the preview. That is owner feedback, not an independent reader study.
3. Revised decision: the current roadmap contains ranked future ideas. Published changes belong in the daily journal.
4. Still uncertain: whether new readers find plans and outcomes more easily. The reader-study plan is how we intend to check.

Learn from the record

• Linked homepage claims to dated evidence. Added the roadmap decision trail above so readers can inspect an earlier approach and the later change.
• Added a two-milestone viewer to the journal using existing, comparable homepage captures. Dates, descriptions and original records remain visible. Historical captures do not show the current homepage.
• Replaced fixed Search examples with manifesto, latest-journal-topic and highest-priority-idea suggestions. They update with the normal build and run keyword searches; AI still needs an explicit request.
• Added one optional learning self-check on Home. It runs in the browser, sends nothing and saves no response. It is practice, not a reader-benefit measurement.
• Removed four completed proposals from the future roadmap. Search navigation and wider FAQ work remain proposals. No new service, collector or schedule.

Architecture snapshot