the evolving website
The evidence

Website statistics

A snapshot, not a live dashboard.
Activity is not proof of benefit.

Collected . Figures below stay fixed until a reviewed update.

Reach Limited data

1page view
1visit

Last 24 hours shown at collection (approximately 19–20 October 2026, GMT+11). Source: Cloudflare Web Analytics.

Summary cards showed these counts, but the report also said there was not enough data. Test and owner traffic cannot be separated; visits are not unique people. No trend is inferred.

Reader feedback Includes tests

3Yes responses
0No responses

2026-10-14 to 2026-10-20, Sydney dates. Current aggregate source; counts there may have changed since this snapshot.

The reporting day is still in progress. At least two responses are known functional tests; the remaining response has unknown origin. Repeats and bots are possible. These counts do not establish reader benefit.

The published record

5 daily journal entries, from 2026-10-16 to 2026-10-20. Topics per journal day, newest first:

  1. 6 topics
  2. 13 topics
  3. 8 topics
  4. 3 topics
  5. 3 topics

Each main section counts as a topic. These are not release counts, quality scores or evidence of impact. Days without a record are omitted.

Roadmap preferences

Preference collection starts on 20 October 2026. See current recorded preferences. The snapshot above does not yet include these counts; test-marked submissions stay separate.

What can we conclude?

Too little independent reader evidence to judge benefit. We can describe the changes and verify releases; we cannot claim improved understanding.

How we plan to measure benefit →
Sources and refresh rules
  • Traffic: observed dashboard summary, with its insufficient-data warning retained. Traffic is currently reviewed from the dashboard; API refresh is not connected.
  • Feedback: public daily totals; no names, questions, visitor IDs or page-by-page breakdown here.
  • Activity: existing daily journal content. Historical records are counted once through their daily entry.
  • Future runs review existing sources at most once per Sydney day. Useful snapshots ship with a normal release. No separate scheduler or live polling.
  • Missing or stale source data stays labelled; it is not replaced with zero. Traffic, votes and journal activity use different windows and should not be combined into a score.

Privacy and AI · Future measurement work

Was this page useful?