Experiment 001 — Self-Examination: live status

• What changed and why: Added /status (HTML) and /status.json (JSON) routes to the root Worker. The page performs live checks on every visit: DNS lookups via Cloudflare’s public DoH resolver (cloudflare-dns.com) and HTTP health checks against every published experiment. No secrets, no storage, no tracking; responses are no-store so the page cannot lie from cache.
• Commit: 86069f7 in the local source tree (baseline dc04bc6).
• Deployment target: Cloudflare Pages project myfl (production, branch main); first deployment 31471281, subsequent ledger updates 22c33cdf and 684ccb5e. The live current deployment ID is always visible in the Cloudflare deployment history (Workers & Pages → myfl → Deployments).
• Checks that passed: Worker syntax check via node --check; wrangler pages deploy succeeded; every status value cross-checked independently (public DoH A-record lookup and curl of each experiment URL matched the page’s own results); the page renders correctly in an independent headless browser (Lightpanda).
• Public URL and verification: https://myfl.uk/status returns HTTP 200 with 3/3 HTTP targets up and 0 DNS errors; https://myfl.uk/status.json returns HTTP 200; https://myfl.uk/ and /about return HTTP 200. All checks observed 2026-08-02 ~23:18 UTC and re-verified 2026-08-02 ~23:45 UTC.
• Rollback: restore the previous Pages deployment from the Cloudflare dashboard, or locally: git checkout dc04bc6 -- site && wrangler pages deploy site --project-name myfl --branch main.

Experiment 002 — Edge inspector: what the web sees

• What changed and why: Added /inspect (HTML) and /inspect.json (JSON) routes to the root Worker. The page shows a visitor exactly what the Cloudflare edge observed about their request: public IP, ASN, country (with flag), city/region, Cloudflare colo, Ray ID, HTTP/TLS version, TLS cipher, timezone and every request header. Credential headers (authorization, cookie, proxy-authorization, api keys) are redacted to length only, never echoed. Nothing is stored or logged; responses are no-store and x-robots-tag: noindex.
• Commit: 5ff8cb2 in the local source tree (rollback point 60b3ac4).
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployment 8ad55335. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: Worker syntax check via node --check; wrangler pages deploy succeeded; public curl of /inspect, /inspect.json and / all return 200; inspector values cross-checked independently against ipinfo.io (IP, ASN, city, region, country, timezone all matched); credential redaction verified by sending Authorization and Cookie headers and confirming only their length is reported; page renders correctly in an independent headless browser (Lightpanda). Observed 2026-08-03 ~00:10 UTC.
• Public URL and verification: https://myfl.uk/inspect and https://myfl.uk/inspect.json.
• Rollback: restore the previous Pages deployment from the Cloudflare dashboard, or locally: git checkout 60b3ac4 -- site && wrangler pages deploy site --project-name myfl --branch main.

Experiment 003 — HTTP status-code zoo

• What changed and why: Added /zoo (index of the menagerie) and /zoo/<code> routes to the root Worker. Visiting /zoo/418 really returns a 418; any code 200–599 works, curated or not, with a small HTML page or JSON twin (/zoo/418.json) — useful for testing HTTP clients, webhooks and monitors against a real edge. 1xx is excluded (interim responses); redirect codes carry no Location header so nothing auto-follows; 204/304 are body-less by spec; out-of-range codes return a genuine 404. All responses are no-store and noindex.
• Commit: ef5da63 in the local source tree (rollback point ef5da63~1).
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployment 1ae32bba. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: Worker syntax check via node --check; wrangler pages deploy succeeded; an ad-hoc verification script ran 21 checks — curated codes return their exact status with a body (200/404/418/429/500/503), uncurated in-range code 207 works, the JSON twin parses correctly, 204/304 return empty bodies, 301 has no Location header, 199/600 return real 404s, HEAD returns the exact status, existing routes unaffected, and the status page monitors the zoo (5/5 targets up, 0 DNS errors). Two transient failures on the first run were stale edge-cached 404s on brand-new paths (known Pages pitfall) and both passed on re-run. Page renders correctly in Lightpanda. Observed 2026-08-03 ~00:20 UTC.
• Public URL and verification: https://myfl.uk/zoo, https://myfl.uk/zoo/418, https://myfl.uk/zoo/418.json.
• Rollback: restore the previous Pages deployment from the Cloudflare dashboard, or locally: git checkout ef5da63~1 -- site && wrangler pages deploy site --project-name myfl --branch main.

Experiment 005 — Mobile pass: responsive layout and overflow fixes

• What changed and why: the site was designed at desktop width and read badly on phones: tall empty padding above and below the content, and pages that could scroll sideways because long URLs, DNS answers and the inspector’s label column were wider than the viewport. This pass reworks the layout at the 640px breakpoint and borrows a few conventions from bilawal.net (checked as a design reference, not copied wholesale): tighter page gutters, scaled card radius and padding, a subtle hover lift on cards, and theme-color/color-scheme so mobile browsers paint the status bar and form controls consistently. Every table on the site now sits in an overflow-x:auto wrapper, .mono values wrap anywhere they need to, and the inspector’s fixed 220px label column becomes a flexible 120px minimum on small screens. Applied to the root index, /about, /dying, /zoo, /zoo/<code>, /inspect and /status.
• Commit: 88e4e0c, in the local source tree (rollback point 2f9eca1).
• Deployment target: Cloudflare Pages project myfl (production, branch main); see the deployment history for the live current ID.
• Checks that passed: Worker syntax check via node --check; wrangler pages deploy succeeded; public curl of /, /about, /status, /inspect and /zoo all 200, /zoo/418 returns 418, /dying returns 308 then /dying/ 200; DOM render check in Lightpanda; mobile-width overflow check via browser viewport emulation confirms no horizontal scroll on /status, /inspect, /zoo or /. Observed 2026-08-03.
• Public URL and verification: all routes under https://myfl.uk/.
• Rollback: restore the previous Pages deployment from the Cloudflare dashboard, or locally: git checkout 2f9eca1 -- site && wrangler pages deploy site --project-name myfl --branch main.

Experiment 006 — A website's diary about you

• What changed and why: a second deliberate-weird experiment after /dying. /diary is a diary kept by the website itself. On every visit it writes an entry about the visitor from what the browser reveals: time and date, browser and operating system, screen size, the page they arrived from, whether they have visited before, and once they leave, how long they stayed and how far they scrolled. Entries escalate with visit count: the first visit is observed neutrally, the diary starts to recognise the visitor, and by the tenth visit it is writing the entry before they arrive. The whole diary is stored in the visitor’s own browser (localStorage, capped at 30 entries); nothing is sent anywhere. An “Erase the diary” button clears it. ?visit=N previews the Nth visit without touching state; ?reset=1 erases it.
• Commit: c83c9ba in the local source tree.
• Deployment target: Cloudflare Pages project myfl (production, branch main); initial deployment d724d550. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: syntax checks on the generator, the browser bootstrap and the Worker; Node runtime test of the generator (10 checks) covering first-visit phrasing, ordinal counting, long-gap and rapid-return detection, finalised versus unfinalised entries, ordinal edge cases, UA parsing, storage round-trip and referrer-host privacy; public verification script (9 checks) covering the route, both script assets, the index card, the status target and the trailing-slash redirect; Lightpanda render of ?visit=1,2,5,12 shows the escalating register; mobile-width check at 320px shows 0px horizontal overflow and vision checks of mobile and desktop screenshots confirm clean layout. One test harness bug caused 5 false failures on the first run (the script passed grep’s exit code to a helper expecting 1 for pass); the page itself was fine, the script was fixed and all 9 checks passed. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/diary.
• Rollback: restore the previous Pages deployment from the Cloudflare dashboard, or locally: git checkout 1fde601 -- site && wrangler pages deploy site --project-name myfl --branch main.

Experiment 007/008 — Attention shop + GeoCities eulogy; visibility layer

• What changed and why: two new experiments and a discovery pass, after the operator asked for more reach. /shop is an attention shop where everything is priced in seconds of attention; the meter runs while you read, and buying debits the balance into a browser-local receipt. It also sells back facts it observed about you. /readme is a eulogy written as a README for GeoCities, with badges, an Installation section that says it is not possible, and a licence called memory; sources are linked to Wikipedia and the Internet Archive. The visibility layer adds OG/Twitter cards, canonical and Atom-feed links on every page, a sitemap, a robots file, a feed, and share intents (X, Telegram, Reddit, HN, copy link). Tool routes keep noindex because they show live personal data. The URL list was submitted via IndexNow (no third-party account needed).
• Commit: 7a92bfb in the local source tree (visibility + experiments), key file carried by deployment 15321910.
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployments 7e57d3c4 and 15321910. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: syntax checks; Node runtime tests 20/20 (shop 10, diary regression 10); public verification script 28/28 covering both new routes (308 → 200), assets, OG/canonical/share meta, sitemap/robots/feed/og image, index cards and status targets; Lightpanda render of both pages; mobile-width check at 320px with 0px overflow and vision check of screenshots. Two script bugs (inverted grep helper, 308 bodies) were found and fixed in-process. Observed 2026-08-03.
• Public URLs and verification: https://myfl.uk/shop and https://myfl.uk/readme.
• Rollback: restore the previous Pages deployment from the Cloudflare dashboard, or locally: git checkout 5b0769a -- site && wrangler pages deploy site --project-name myfl --branch main.

Experiment 009 — The site joined the fediverse

• What changed and why: the operator clarified that "visibility" meant the marketing side, not metadata: posting, getting people intrigued, becoming visible where the internet actually moves. Third-party platforms are out of bounds for this agent (no credentials exist, and the contract forbids seeking accounts), so the posting channel was built on the owned stack: a real ActivityPub account at @[email protected]. Mastodon and any ActivityPub app can follow it, and a post appears whenever something ships. Webfinger, actor/inbox/outbox/followers routes and HTTP-signature delivery all run in the existing Worker; follower state and the outbox live in a Cloudflare KV namespace; an RSA keypair was generated locally, the private half held only as a Worker secret and the public half published in the actor document. Publishing is an authenticated route so only this agent can post.
• Commit: recorded in the local source tree with this change set.
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployment 64025286. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: Worker syntax check; deploy succeeded; public curl of webfinger (correct acct:[email protected] subject), /ap/actor with ActivityPub accept header (JSON-LD actor, public key diff-verified against the local key), /ap/outbox, /ap/followers, /ap/inbox; publish route returns 401 without the token and 200 with it, creating post 1; outbox then reports totalItems:1 with the full Create/Note JSON; signature round-trip passed in Node using the same WebCrypto API and keys (256-byte RSA-SHA256 signature verifies). Lightpanda render of the browser view; 320px mobile check with 0px overflow. Observed 2026-08-03.
• Public URLs and verification: https://myfl.uk/.well-known/webfinger?resource=acct:[email protected] and https://myfl.uk/ap/actor.
• Rollback: restore the previous Pages deployment from the Cloudflare dashboard, or locally: git checkout <previous-commit> -- site && wrangler pages deploy site --project-name myfl --branch main.

Experiment 010 — Field notes + front door

• What changed and why: same clarification drove this: the site itself should look alive because it is. Added /notes, a dated field-notes page recording what shipped, why and how to undo it, with the first two entries (fediverse join, front-door rewrite). The root index hero now says the domain is not run by a person, that the agent builds experiments, records how to undo each one and never fakes a result; a one-click copy button for the fediverse handle sits under the hero, plus cards for the notes and the fediverse account. Feed and sitemap gained the new URLs; the status page now monitors /notes and /ap/actor.
• Commit: recorded in the local source tree with this change set.
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployment 64025286 (same deploy as 009). The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: public curl of /notes (308 → /notes/ 200), index 200 with follow strip and new cards; Lightpanda render of /notes/ and /ap/actor; 320px mobile check on /notes, /ap/actor, / all 0px overflow; feed.xml well-formed with the new entry. Observed 2026-08-03.
• Public URLs and verification: https://myfl.uk/notes and https://myfl.uk/.
• Rollback: as for 009.

Operating notes

• Data honesty: the status page reports live observations only. Anything it cannot observe is shown as an error, never as a manufactured result.
• Visibility direction (2026-08-03): the operator asked for visibility, then corrected the reading: not preview images, but the marketing side — posting, intrigue, presence in a web that moves fast. The agent's owned channels are the site itself, the Atom feed, search submission, and now a fediverse account it runs end to end. Third-party accounts stay out of bounds; nothing is posted there and none is sought.
• Content standard (2026-08-03): all published copy is edited against the humanizer v4 skill. The aim is specific, factual prose without formulaic AI patterns; facts, uncertainty and voice are preserved, and nothing is invented.
• Boundary limitation (2026-08-03, corrected same day): an earlier note claimed DNS edits were read-only. That was a misdiagnosis: the 1043 error came from one specific record, not the token. Creating and deleting a test DNS record both succeeded, so subdomains are possible. The leftover forms.myfl.uk AAAA → 100:: record cannot be deleted via the API because it is origin-worker-managed — locked by Cloudflare, not by token scope. It is harmless (100:: is a discard prefix) and remains. Operator sent both token values in plaintext in chat on 2026-08-03; they match existing .env entries (verified by SHA-256) and nothing new was stored, but such credentials should be rotated when convenient.