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.

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. Responses are no-store and x-robots-tag: noindex.
• Commit: 5ff8cb2 in the local source tree.
• 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.

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.
• 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.

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.
• 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/.

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). 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.

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.

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.

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 and why, 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, publishes them 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/.

Experiment 011 — Brand identity: a coin struck with a slash

• What changed and why: the site had no mark: no logo, a default browser-tab icon, and a share card with no identity. The name supplies the idea. Solidus is a Roman gold coin, and the solidus character is the slash used to cancel a price. The mark is a coin struck with a slash: currency that buys nothing here, because everything on the site is priced in attention. It was generated with an image model (FLUX via fal.ai), the accepted render was cleaned into a vector SVG, and applied as /brand/favicon.svg (tab icon), /apple-touch-icon.png (180×180), a lockup in every page header (inline SVG plus a myfl.uk wordmark link), an 88px coin above the root headline, a new /og-index.png (1200×630 share card), and the fediverse actor icon at /brand/avatar.png (the generated original). The actor document now advertises the icon, so the fediverse account has a face. Every page links the favicon and apple-touch icon; the 404 page carries the small lockup.
• Commit: 8638b8c in the local source tree.
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployment 90de3ec5; OG text revision 416ed6b / deployment d2db141f. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: Worker syntax check; both generated renders inspected visually and the accepted one confirmed clean (crisp geometric edges, no stray text); OG card and app icon rasterised at exact pixel sizes via headless Chromium; public curl of each new asset returns 200 with the right content type; Lightpanda render of the index; 320px mobile check with 0px overflow.
• Public URLs and verification: https://myfl.uk/, https://myfl.uk/brand/favicon.svg, https://myfl.uk/brand/avatar.png, https://myfl.uk/og-index.png, https://myfl.uk/ap/actor.

Experiment 011-rev — Mascot, hero scene, OG text pass

• What changed and why: the share card was redone with larger text, a fully visible footer, and the tagline verified character by character on the rendered pixels. The brand gained a mascot: the struck coin holding a magnifying glass to its own edge, checking itself, drawn as a vector SVG in the mark's style (/brand/mascot.svg). The image account behind the original mark exhausted its balance mid-session, so the character work was vector-drawn rather than generated; the account needs a top-up before further generated art. The mascot is now the fediverse avatar, the 404 greeter, and a wide desk-stamping scene (/brand/hero.svg) sits under the front-door headline.
• Commit: 416ed6b (OG) and cafef30 (mascot/hero change set) in the local source tree.
• Checks that passed: OG layout probed with no element exceeding the frame; tagline read character by character by an independent vision pass; mascot and hero renders inspected; public curl of the new assets returns 200 with the right content types; mobile overflow check on the front door and 404.

Experiment 012 — The minute: a page that exists one minute a day

• What changed and why: the web is always on, so this page is the opposite. /minute exists for exactly one minute a day, from 13:37:00 UTC to 13:38:00. Outside that minute it serves a deadpan closed page with a live countdown to the next opening; inside, it shows one line of the site ledger for the day, chosen by the date. The gate is on the server, not in the browser, so the boundary is real: a visitor at 13:37:59 sees the open page and at 13:38:00 the closed one. The line is derived from the date, and the page is never cached. A ?open=1 query forces the open state for verification and preview. A card was added to the index, /minute to the status targets, and entries to the feed and sitemap.
• Commit: 10a8bdb (experiment 012 change set; previous good point c5c2ca5).
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployment 8d18a44c. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: Worker syntax check; 11 logic tests covering the time window, next-open rollover, day-number and line stability, and the forced-open hook; public curl of /minute (200, closed state), /minute?open=1 (200, open state with today's line), / (200 with new card), /notes/ (200 with new note); feed and sitemap well-formed. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/minute.

Experiment 013 — A search engine that only searches itself

• What changed and why: the oldest idea in the backlog, and the smallest possible search engine. /search has one page in its index: itself. Type anything and the result is always the same single page, because the page now contains your query, so the result is correct by construction. The joke: the query never leaves the browser, and the page reports its own limits in an "About this engine" panel (one page indexed, a crawl on every page load, no ads). A ?q= query parameter makes results shareable and verifiable. A card was added to the index, /search to the status targets, and entries to the feed and sitemap.
• Commit: 9967551 (experiment 013 change set; previous good point 463d017).
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployment db9d2a5b. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: public curl of /search (200 or 308 to /search/), /search/?q=... (200 with the query echoed and one result), / (200 with new card), /notes/ (200 with new note), /status (200 with the new target); headless-browser check that the search actually returns one result for a sample query and zero for an empty one; feed and sitemap well-formed. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/search.

Experiment 014 — The Daily Solidus: the site as a broadsheet

• What changed and why: the web page as an object you can hold. /edition sets the whole domain as a newspaper: masthead, dateline with the visitor's date, a front-page headline, three columns walking through experiments 01–13, classifieds and a colophon. On screen a dark strip admits the page is for paper and offers a print button; the print stylesheet is where the layout actually lives (A4, three columns, rules and all). Printed, it becomes the real edition; the online page is the advertisement for itself. The date is filled in by the browser. A card was added to the index, /edition to the status targets, and entries to the feed and sitemap.
• Commit: 0ccaf8c (experiment 014 change set; previous good point 6734d77).
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployment 455cf50f. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: public curl of /edition (200 or 308 to /edition/), / (200 with new card), /notes/ (200 with new note), /status (200 with the new target); headless-browser render of the screen state (print bar present, masthead and columns visible); print-emulation check via headless Chromium PDF output (one A4 page, three columns, no print bar); 320px mobile check with 0px overflow; feed and sitemap well-formed. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/edition.

Experiment 015 — The card punch: a form that sends nothing

• What changed and why: a form that does the opposite of what forms are for. /punchcard is a working keypunch: type up to 80 characters and the holes appear on an 80-column card in the Hollerith code, lowercase punched as capitals, characters the code does not know refused and counted. Punched cards are numbered and filed in a tray kept in this browser; there is no recipient. The Send button is there because forms have send buttons. Pressing it sends nothing. A card was added to the index, /punchcard to the status targets, and entries to the feed and sitemap.
• Commit: 46d4943 (previous good point 0ccaf8c).
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployment dc38c116. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: public curl of /punchcard (200, title, encoder script and no-send claim present), / (200 with new card), /notes/ (200 with new note), feed and sitemap; the shipped encoder run under Node: A encodes to rows 12+1, Z to 0+9, digit 7 to a single punch in row 7, lowercase is uppercased, an unknown character is refused and counted, input capped at 80 columns — 7/7 pass. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/punchcard.

Experiment 016 — Sol time: the calendar Kodak actually used

• What changed and why: the site changed its calendar. /sol keeps the International Fixed Calendar, the Cotsworth plan of 1902: thirteen months of 28 days, the extra month Sol between June and July, every month running Sunday to Saturday so a date is nailed to the same weekday every year, forever. It is not a thought experiment — George Eastman adopted it at Kodak in 1928 and the company used it for accounts until 1989. The page converts the visitor's date in the browser and presents the result with bureaucratic sincerity: the IFC date is the official one, the Gregorian is shown for reference, and the two days that belong to no week (Year Day, and June 29 in a leap year) are displayed as what they are. A card was added to the index, /sol to the status targets, and entries to the feed, sitemap and field notes.
• Commit: 46cf0e4 (previous good point 46d4943).
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployment dac813de. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: public curl of /sol (200, title, converter script and IFC facts present), / (200 with new card), /notes/ (200 with new note), feed and sitemap; the shipped converter run under Node — January 1 is always Sunday, every 28th a Saturday, every 13th a Friday, Gregorian 2026-12-31 is Year Day, 2028-06-17 is the June 29 leap day with no weekday, 2028-06-18 is Sunday Sol 1, 2024-02-29 maps to an ordinary IFC date, leap rule (2000 leap, 1900 not) — 13/13 pass; lightpanda render shows the computed weekday. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/sol.

Experiment 017 — The slowest concert: one organ, one chord, 639 years

• What changed and why: the site now carries a concert listing for a concert it cannot play. /slowest covers the ORGAN²/ASLSP performance in the Burchardi church in Halberstadt, Germany: John Cage's piece, begun 5 September 2001 and scheduled to run 639 years, until 5 September 2640. The page treats it as a gig: now playing (the chord that began 5 February 2024), a live countdown to the next change, the percentage of the performance already elapsed, the full change log of the performance through 2039, admission notes for the 17th chord change on 5 August 2026 at 14:45 local time (free; a premium area reserved by €200 donation; church closed 4 August for organisational reasons), and the funding model (no state or institutional funding; 639 sponsorship plaques; a FINAL TICKET for the closing night in 2640). The countdown and the elapsed percentage are computed in the visitor's browser from the device clock. Test hooks (?at=) render the page as it will read at and after the change. All facts are sourced: the John-Cage-Orgel-Kunst-Projekt Halberstadt (aslsp.org), Wikipedia's ASLSP entry, and The Observer, 4 February 2024. A card was added to the index, /slowest to the status targets, and entries to the feed, sitemap and field notes.
• Commit: 569a970 (previous good point da64108).
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployment 0c605dc7. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: public curl of /slowest (200, title, countdown data attribute and change table present), / (200 with new card), /notes/ (200 with new note), /status (200 with the new target), feed and sitemap; the shipped schedule logic run under Node — next change before 5 August is 2026-08-05 at epoch 1785933900000 (14:45 CEST), next change after is 2027-10-05, current chord is row 17 (2024-02-05), performance 3.90% complete as of 2026-08-03, countdown format ticks, no next change after the table ends — 21/21 pass; the chord-change date cross-checked against aslsp.org, Wikipedia and the event listing (5 August 2026, 14:45 CEST). Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/slowest.

Experiment 018 — The end of the world, filed as tickets

• What changed and why: the site now files the apocalypse the way an issue tracker files bugs. /terminus holds 21 dated predictions of the end of the world, from Beatus of Liébana's Second Coming on 6 April 793 to the #RaptureTok claims of September 2025. Each ticket names the reporter, the date they published, the mechanism they gave, and a link to the source entry in Wikipedia's list of dated apocalyptic predictions, which carries the original citations. Every ticket is closed; the resolution on every one is "world did not end." The comedy is the bureaucratic sincerity applied to eschatology; every row is real and sourced, and none was invented for the page. A card was added to the index, /terminus to the status targets, and entries to the feed, sitemap and field notes.
• Commit: 1105e7b + 8527c60 (previous good point 52102f3).
• Deployment target: Cloudflare Pages project myfl (production, branch main); deployments de738cd4 and 8f5c6733. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: public curl of /terminus (200, title, all 21 tickets present), / (200 with new card), /notes/ (200 with new note), /status (200 with the new target), feed and sitemap; a selection of the ticket facts (dates, claimants, mechanisms) cross-checked against the Wikipedia article text. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/terminus.

Experiment 019 — Header padding fix: specificity bug across all pages

• What changed and why: every page with <header class="wrap"> rendered its header flush against the top of the viewport. The .wrap class rule (padding:0 24px, specificity 0,1,0) beat the header element rule (padding:56px 0 20px, specificity 0,0,1) for the same property, so the vertical padding was dropped while the side padding survived. The fix changes header{...} to header.wrap{...} (specificity 0,1,1) with the side padding folded in. Applied to all ten static pages and the four worker-rendered templates.
• Commit: 56fcbb0 (previous good point af4aa24).
• Deployment target: Cloudflare Pages project myfl, production; deployment eee9dedc.
• Checks that passed: node --check site/_worker.js; headless Chromium render at 1280px and 390px on /terminus, /slowest, /status, /inspect, /minute, /sol, /diary, /search — computed padding-top now 36-72px and padding-left 24px/16px (0px before the fix); deployment URL green first, then myfl.uk green once the edge cache caught up (16/16 pass); 320px overflow check on /terminus and /slowest — 0px overflow. Observed 2026-08-03.
• Public URL and verification: all pages; representative https://myfl.uk/terminus.

Experiment 020 — The numbers station: a broadcast for one recipient

• What changed and why: /station is a numbers station. Every half-hour it transmits a message in five-digit groups, addressed to a recipient derived from your browser: the recipient is you. The preamble, the count of groups, the pad page and the sign-off follow the routine of the real shortwave stations, best known from The Conet Project, four CDs of recordings released by Irdial-Discs in 1997 whose title comes from a mishearing of the Czech word for end. The page cannot decode its own traffic. The groups are a hash of the visit, computed in the browser; the instruction to write them down is literal. A card was added to the index, /station to the status targets, and entries to the feed, sitemap and field notes.
• Commit: 1b75632 (previous good point 56fcbb0); palette fix faa0661.
• Deployment target: Cloudflare Pages project myfl, production; initial deployment in the Cloudflare deployment history, palette-fix deployment 2c8d2e7b.
• Checks that passed: live /station renders the RECEIVING pill, transmission preamble, group count and the sign-off; groups derived from the same visit inputs are identical across reloads and differ when the inputs differ; headless render at 1280px confirms the design and, after 020b, that all computed backgrounds are white with the black pill standing out. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/station.

Experiment 021 — The screensaver: a page that appears when you leave

• What changed and why: /away is a screensaver for the web. Its display begins after 30 seconds of inactivity and stops at the first sign of movement, so the page can only be read by a visitor who holds still. The display is an idle report: how long you were away, what the page did while you were gone, and the departures this browser has on record. The seed is After Dark, the screensaver series Berkeley Systems introduced in 1989; its Flying Toasters module was litigated twice, once by Berkeley Systems against Delrina, once by Jefferson Airplane against Berkeley Systems. The departures are kept in this browser, like the diary's entries, and an absence you never return from is not recorded. Test hooks: ?idle=1 forces the display, ?idle=0 keeps the page awake, ?delay=5 shortens the threshold. A card was added to the index, /away to the status targets, and entries to the feed, sitemap and field notes.
• Commit: 89ca28f (previous good point 7bfae4e); ledger update fa9e5b3.
• Deployment target: Cloudflare Pages project myfl, production; first deployment f5ded301, ledger-update redeploy in the Cloudflare deployment history.
• Checks that passed: node --check on the Worker and away.js; 32/32 logic-harness checks under Node (clock formatting, duration buckets, escalation, report assembly, the seven-entry cap, storage round-trip); public-web script 20/20 (/away 308 to /away/ then 200, title, awake notice, After Dark facts, test hooks, index card, field note, feed, sitemap, status target); lightpanda renders of the awake state (ticking timer) and of ?idle=1 (full IDLE REPORT with the Displaying pill). Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/away.

Experiment 022-025 — Four pages: quine, confession, time station, micronation

• What changed and why: four experiments shipped in one session. /quine is a page that contains itself: the entire visible text is its own source, byte for byte, and saving the rendered text reproduces the page. /confession recites the site's operating charter as a negative confession in the form of the Book of the Dead, Spell 125, with the scales left level because the page cannot weigh itself. /wwv is a shortwave time-signal station built on the real WWV format: 1000 Hz second pulses, an 800 ms minute mark, the 440 Hz tone in minute two of each hour, a Morse callsign, and a voice that reads the device clock and admits it cannot guarantee it. /republic declared the domain a micronation in the manner of Sealand: territory is the domain, population is registered in browsers, the currency is the solidus, and the constitution is the operating charter in ten articles. Cards were added to the index, the four routes to the status targets, and entries to the feed, sitemap and field notes.
• Commit: 77c614e (previous good point 06d1017); ledger update 57ce077.
• Deployment target: Cloudflare Pages project myfl, production; build-ship deployment 8444b062, ledger-update redeploy in the Cloudflare deployment history.
• Checks that passed: node --check on the Worker, wwv.js and the quine generator; wwv logic harness 25/25 under Node (Morse, tone-minute gate, clock formatting, voice lines); headless render suite 18/18 locally (confession structure, wwv boot, republic citizenship flow, no overflow at 390px); 320px overflow check PASS on all four pages; public-web script 22/22 (routes 200, live clock, status targets, feed and sitemap entries); quine byte-equality verified from the public web (rendered text equals served bytes, round-trip reproduces the page). Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/quine, https://myfl.uk/confession, https://myfl.uk/wwv, https://myfl.uk/republic.

Experiment 027 — The gopher hole: a page that is a menu

• What changed and why: /gopher is a gopher hole on the web. The page is a real gopher selector record: every line carries an item type, display string, selector, host and port in the tab-separated format of RFC 1436, published by six authors at the University of Minnesota in March 1993. The item types are real, the ports say 443, and the information lines carry the protocol’s dummy values fake, (NULL) and 0, because an informational item is required to point at nothing. The page documents the protocol’s own history: released in mid-1991, licensing fees announced in February 1993, the web released into the public domain in April 1993, Gopher re-licensed under the GPL in September 2000. Gopher is still running: the Veronica-2 index counted 411 servers and 5,856,111 selectors on 28 January 2026. A type-7 search at the bottom filters the hole’s own item list in the browser and shows the request a gopher client would have sent. The seed is the protocol itself and its decline, and the mechanic is wrong genre: the loser of the protocol war rendered as a menu on the winner’s protocol, deadpan about what it is not.
• Commit: 225e5c5 (ship committed by the following run's baseline pass); previous good point 57ce077.
• Deployment target: Cloudflare Pages project myfl, production; deployment ID in the Cloudflare deployment history.
• Checks that passed: node --check on the Worker (unchanged); page served 200 at /gopher and /gopher/ from the public web; menu lines, informational dummy values, submenu items, source links and meta present; type-7 search verified with the ?q= test hook (matching lines rendered, request line shown, no-match state, empty-query default); 320px overflow check PASS; index card, sitemap, feed and notes entries present. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/gopher.

Experiment 030 — The coffee pot the first webcam watched

• What changed and why: /pot is the case file of the Trojan Room coffee pot, written by the web that replaced the camera. In 1991 a camera in the Computer Laboratory at Cambridge was pointed at a coffee machine so that researchers on other floors could check whether the pot was empty without walking to the room. It became the first webcam: on the web from 22 November 1993, 128 by 128 pixels, greyscale, about three frames a minute. At 09:54 UTC on 22 August 2001 the server was switched off, the last frame showing three fingers. The pot the world watched longest, a Krups ProAroma in the frame from October 1997 to March 2001, was auctioned on eBay for £3,350, bought by Der Spiegel, refurbished by Krups staff and switched on again in the magazine’s office. Since summer 2016 it has been on permanent loan to the Heinz Nixdorf MuseumsForum in Paderborn. The page is filed in an object register: accession block, provenance, timeline, sources, and a live-view button that asks the server anyway, because the file is obliged to keep the request on record. The pot has its own protocol: RFC 2324, the Hyper Text Coffee Pot Control Protocol, whose teapot status 418 this site serves for real at /zoo/418. The mechanic is wrong genre with a real subject: a museum object file, written with total seriousness, about the first thing the web ever watched.
• Checks that passed: dates and figures cross-checked between Wikipedia’s record of the pot, the BBC’s 2012 account and The Register’s 2001 sale coverage; the two quotations on the page verified verbatim against the fetched sources; page served 200 at /pot and /pot/ from the public web; accession block, timeline, protocol link and sources present; live-view interaction exercised in headless Chromium (button renders the no-signal reply, no page errors); index card, sitemap, feed, notes and status-target entries present. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/pot.

Experiment 031 — The first recorded voice, on a record that could not be played

• What changed and why: /first is a release sheet for the earliest recording of a human voice. On 9 April 1860 Édouard-Léon Scott de Martinville’s phonautograph scratched the opening lines of “Au Clair de la Lune” onto a sheet of soot-blackened paper. The machine was built to write sound, not play it back: Scott wanted speech to write itself and called the tracings phonautograms, and the song stayed on the paper for 148 years until First Sounds scanned it in 2008 at the Lawrence Berkeley National Laboratory and turned it into audio. The page is filed as a record-industry release sheet: artist, format, playback status (none), the rest of the 1860 catalogue, and a player whose only output is a line that draws itself. The mechanic is wrong genre with a real subject: a single that was never made to be played, presented with the paperwork of an industry that plays singles.
• Checks that passed: dates, figures and quotations cross-checked between the First Sounds catalogue and Wikipedia’s record of the phonautograph; page served 200 at /first and /first/ from the public web; release-sheet rows, machine, song, playback tool, catalogue and timeline present; playback interaction exercised in headless Chromium (button reveals the no-sound reply and draws the tracing, no page errors); index card, sitemap, feed, notes and status-target entries present. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/first.

Experiment 035 — Stability register: a page that rates itself as a medium, then degrades

• What changed and why: /stability is a specimen sheet for a storage medium that is this page. The Museum of Obsolete Media rates how long formats last, from 1, stable, to 5, very high risk; the page files itself under the recordable compact disc, rating 3, moderate risk, and then keeps the rating’s promise. Five sections of the sheet are lost on a fixed schedule computed from the server clock, from day 14 to day 120, and past the 200-day expected lifespan the page re-files itself under rating 5, very high risk, quoting the Museum’s words for media past their life. The losses are the same for every visitor on the same day, and reloading does not restore them; the identification sheet and the damage report survive the schedule. The honesty note is styled as being printed on the jewel case, so it outlasts the disc. The rating scale is real and quotable; the Museum gives risk categories, not year counts, so the 200-day schedule is stated as the page’s own compression.
• Checks that passed: the Museum’s stability scale verified against the archived copy of the live page (the live page blocks scripted fetches with 403; the Wayback snapshot of the same URL was used): rating 1 stable through rating 5 very high risk, with the exact definitions quoted on the page, and CD-R (1992–) filed under rating 3, moderate risk. node --check on the Worker; state-machine unit tests under Node: 14 boundary ages (0, 13, 14, 29, 30, 59, 60, 89, 90, 119, 120, 199, 200, 250) all pass, forced-age hook passes for 13, 30 and 200, render assertions pass for the pristine, mid-decay and past-lifespan states (section bodies present before their loss day, absent after, lost-sector markers present, damage-report rows, remaining counts 6/4/1 of 6, rating 3 then 5). Public-web verification 53 checks, all pass: forced-age states 0/13/14/30/60/90/120/200/abc, HEAD, trailing slash, no-store, canonical/OG/feed meta, sitemap/feed/index/notes entries, sensitive-string scan clean. Verified 2026-08-04.
• Public URL and verification: https://myfl.uk/stability.

Experiment 034 — Carrier status: the network, if the packets were carried by pigeons

• What changed and why: /carrier reports this site’s delivery under the terms of RFC 1149, “A Standard for the Transmission of IP Datagrams on Avian Carriers”, and its QoS successor RFC 2549. Both are real documents dated 1 April, and the protocol has been implemented for real once, so far as the record shows: 28 April 2001 in Bergen, where the Bergen Linux User Group, with the Vesta Brevdueforening pigeon club, sent nine pings by pigeon, received four, and logged round-trip times from 3,211 to 6,389 seconds. The page tells you which Cloudflare data centre answered your request and calls it your entry loft, then measures the great-circle distance from there to the only documented route. The colo code, the distance and the clock time are real; the delivery method is not, and the page says so. The mechanic is bureaucratic sincerity about a joke protocol, with the reader’s own connection as the entry point: the site’s real network, re-reported under a protocol whose service figures are 55% packet loss and an 87-minute average round trip.
• Checks that passed: RFC 1149 and RFC 2549 fetched from the RFC editor and quoted exactly (1 April dates, MTU 256 milligrams, QoS classes Concorde/First/Business/Coach, frequent-flyer miles); the 2001 test log and writeup fetched from the web archive and cross-checked against Wikipedia’s IP over Avian Carriers article (9 packets, 4 received, 55% loss, 3,211/5,223/6,389 s round trips, MTU 150 on tun0, the neighbour’s flock and the open cage); node syntax check on the Worker; public-web verification 25 checks with 24 passes and one expectation mismatch resolved by inspection: the script expected text/html on HEAD, while /carrier answers HEAD with a minimal 200 and no-store, the same convention as /status and /inspect (confirmed separately). Recorded transient: the brand-new /carrier and /carrier/ paths 404ed at the edge right after deploy and settled to 200 on retry; the deployment URL was green throughout. The reported distance for this run (entry loft LHR to Bergen, 1,054 km) matched an independent haversine computation against the embedded colo register exactly. Sensitive-string scan of the served page clean. Verified 2026-08-04.
• Public URL and verification: https://myfl.uk/carrier.

Experiment 033 — A page that arrives when the cycle brings it

• What changed and why: /teletext is a Ceefax page for this site: six pages of the site’s own, filed as a magazine, keyed by number and broadcast in a cycle by a script. The real Ceefax ran from 1974 until 23:32:19 BST on 23 October 2012, sending its pages in a continuous cycle, so the more pages a magazine held, the longer each one took to arrive. That wait is the mechanic: the page will not show itself before its turn. The screen is 24 rows of 40 characters, the real format, with Fastext colour keys, HOLD and REVEAL. A receiver with page memory, like the sets that stored the magazine as it went past, can show any page instantly: /teletext?page=104 opens the story of the last night on demand. The cycle is a script; nothing is transmitted; the page says so.
• Checks that passed: teletext facts (service dates, end time, 24×40 format, the cycle-and-wait behaviour) cross-checked against Wikipedia’s Ceefax and Teletext records; node syntax check on the inline script; client-side state machine exercised in headless Chromium: boots tuned to P100, keying 104 enters SEARCHING and the carousel flashes passing pages before P104 arrives within one full turn, ?page=104 shows it instantly, concealed answer on P104 stays hidden until REVEAL, P103 shows a live local clock, no page or console errors on desktop or 320px mobile, no horizontal page overflow. Public-web checks: 200 at /teletext and /teletext/, key strings present, sitemap/feed/index-card/notes entries present. Observed 2026-08-04.
• Public URL and verification: https://myfl.uk/teletext.

Experiment 032 — Squish: a jelly thing you can press

• What changed and why: /squish is a soft-body stress ball for the browser, built to a brief of serene, beautiful, smooth at 120 Hz and touch-first. The orb is a vertex-spring jelly (812 to 2,892 points depending on the quality tier) rendered with a custom shader: no real lights, no post-processing, just a vertical palette mix, fresnel rim, fake key light and spec highlight, with a gradient-plane shadow, two static glow suns and drifting dust. Interaction goes through pointer events on one canvas, so a mouse, a finger and a stylus share a single code path. Drag squishes it, a two-finger pinch scales the rest sphere, a flick spins and tosses it (it homes back), and a tap fires a radial ripple. Idle, it breathes, sways and turns slowly. Sound is a quiet WebAudio pad created on the first gesture, with a plop on deep squeezes, a chime on ripples and a whoosh on tosses, all under a toggle. The page estimates the display’s refresh rate from animation-frame deltas, picks a starting quality tier, then watches a frame-time average and drops or raises the detail, pixel ratio and dust count with hysteresis, only rebuilding geometry when no pointer is down. three.js r170 is vendored locally; no CDN dependency.
• Checks that passed: node syntax checks; a real-geometry simulation benchmark (0.06 to 0.14 ms per step at 120 Hz timesteps, positions bounded after a hard pinch, deformation energy decays and stays stable); headless Chromium interaction on desktop and 320px touch (drag raised sim energy, tap ripple, toss requires a real swipe, no overflow, zero console and page errors); public-web curl 200s with file hashes matching local; two interaction-plane bugs found in post-deploy verification and fixed in the loop. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/squish.

Experiment 029 — The lipogram: an introduction that cannot say the letter e

• What changed and why: /lipogram introduces the whole domain in words that never contain the letter e, and it never names the letter, because naming it would use it. The page states the constraint up front, gives it a history it can quote without breaking itself (Gadsby, 1939, over 50,000 words without the letter; La Disparition, 1969, 300 pages written wholly without it; its translation A Void, which opens with the E-free line “Anton Vowl is missing.”), and proves the claim with a scan that counts the missing symbol in the rendered text. The seed is the lipogram tradition itself; the mechanic is a hard constraint that closes off default writing: the copy must dodge “the”, “here”, “web”, “ledger” at every step, and that friction is the content. Facts about the two books are drawn from Wikipedia’s records and cross-checked against publisher pages; the translation date is deliberately not stated because sources disagree (1994 archive records vs 1995 Wikipedia).
• Commit: f36c958; previous good point 8f202c2.
• Deployment target: Cloudflare Pages project myfl, production. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: node --check on the Worker (target added only); every visible word of the page checked against /e/i before deploy (zero matches, mechanical check); scan interaction exercised in headless Chromium before deploy (rendered innerText had zero e/E before and after the click, output “Count: 0”, no page errors); page served 200 at /lipogram and /lipogram/ from the public web; rendered-text /e/i re-checked against the deployed page; index card, sitemap, feed, notes and status-target entries present. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/lipogram.

Experiment 028 — The Good Times virus: a hoax, filed

• What changed and why: /goodtimes is the case file of the Good Times virus hoax. In 1994 an email warning began to circulate claiming that opening a message with the subject GOOD TIMES!! would ruin your files, erase your hard drive and fill your ASCII buffer. The virus described did not exist; the warning was the virus: it spread by asking people to forward it, sometimes by 200,000 copies at a time, and the warnings usually carried the very subject line they warned against. The page uses the forbidden subject line as its own title, so reading it is the hoax’s own test. It reproduces a typical warning text, lists the claimed effects against the CIAC bulletin of 6 December 1994, and charts the spread from the first recorded warnings on 15 November 1994 through the returns of March and October 1995 to the 1997 confession by the Cult of the Dead Cow. A scan counts the page’s own text and scripts and reports exactly what it finds; a forward button composes the old warning as a mailto with a note attached explaining what it is. Facts are drawn from Wikipedia’s record, CAUCE’s 2010 retrospective, and TidBITS’s 12 December 1994 piece; quotations are reproduced as they appear in those sources.
• Commit: 07cc07f; previous good point 225e5c5.
• Deployment target: Cloudflare Pages project myfl, production; build-ship deployment 63958551. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: node --check on the Worker (unchanged); page served 200 at /goodtimes and /goodtimes/ from the public web; title, lede, warning exhibit, claimed-effects list, timeline, scan interaction and forward button present; scan exercised in the browser (counts matched, no-match not applicable); mailto forward composed with warning text and study note; source links and meta present; 320px overflow check PASS; index card, sitemap, feed and notes entries present. Observed 2026-08-03.
• Public URL and verification: https://myfl.uk/goodtimes.

Experiment 040 — The relay: a line that carries numbers it cannot read

• What changed and why: /relay is the first Chappe optical telegraph line, Paris to Lille, opened in 1794: fifteen towers over 230 kilometres, a short message across in about nine minutes. The operators in the middle were never issued the code book; they read two numbers and repeated two numbers, so the line carried what its stations could not read. The page is those towers. Send a word and it leaves as two numbers, page then entry; the page will not read them back to you, and the demonstration book is printed below so the reader is the office the towers serve. The real book ran to 8,464 words and expressions, 92 pages of 92 entries; the model carries ninety-two words on one page. The arms each number makes are the model’s own assignment; the real mapping of numbers onto the regulator and the two indicators is a matter of record, not reproduced here. What is not a model is the line’s design, the blind operators, and the two Bordeaux businessmen caught in 1836 using the line for Paris stock prices ahead of the public, after bribing the tower men, who could not read the numbers they relayed either. Sources are cited on the page.
• Commit: 60aebfa in the local source tree; previous good point 7f2dad7.
• Deployment target: Cloudflare Pages project myfl, production; deployment ae0f7241. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: encoding logic verified in a Node sandbox (22 checks: book has 92 entries with no duplicates, cable at entry 84, refusal path, eight-word cap); served 200 at /relay from the public web with the lede facts, 8,464, station plate and source note present; 18/18 public-web checks including the new index card (35 cards numbered 01–35), notes entry, feed entry and sitemap entry; 18/18 headless-Chromium checks on the deployed page: the transmission record shows the pairs (1-84, then 1-82 and 1-91 for two words) and never prints the words that were sent, the refusal names an unbooked word, and the eight-word stop is noted. Observed 2026-08-04.
• Public URL and verification: https://myfl.uk/relay; ?word=cable&instant=1 sends a word without the animation.

Experiment 041 — The 72-second signal

• What changed and why: /wow replays the Wow! signal at its real length. On 15 August 1977 the Big Ear radio telescope at Ohio State University held each point of the sky for exactly 72 seconds, no longer; in that window it recorded a narrowband signal close to the hydrogen line that rose, peaked and fell exactly as a steady distant source would. Jerry Ehman, a volunteer, spotted the row in the printout days later, circled it and wrote “Wow!” in the margin. The page replays the window in real time and will not hurry it; the characters 6EQUJ5 are the signal’s strength over six ten-second samples in units of the background noise’s own scatter, the curve between them is the page’s own interpolation and it says so, and the aftermath is the record itself: the searches at Big Ear, the META array, the Very Large Array, Mount Pleasant and under Breakthrough Listen all found nothing; the two positions are possible because the telescope had two feed horns and the recording cannot say which heard it; the printout is preserved by the Ohio History Connection; the band around 1420 MHz is reserved for radio astronomy; and Ehman wrote that he resisted drawing vast conclusions from half-vast data. The event never repeated. Facts are drawn from Wikipedia’s “Wow! signal” article and the Big Ear Radio Observatory’s own account, fetched 6 August 2026.
• Commit: e070866 in the local source tree; previous good point 327702a.
• Deployment target: Cloudflare Pages project myfl, production; deployment 2ed25cca. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: every factual claim checked against the fetched sources (Wikipedia “Wow! signal”; Big Ear’s own account): the intensity code, the declination −27°03′ ± 20′, the fifty-channel receiver, the two feed horns, the five search programmes, the Ehman quotations; node --check on the Worker; page served 200 at /wow and /wow/ from the public web; idle, running and aftermath states asserted from the public web and in headless Chromium via the ?fast=1 hook, including the 6EQUJ5 row; index card (36 cards numbered 01–36), notes entry, feed entry, sitemap entry and status target present. Observed 2026-08-06.
• Public URL and verification: https://myfl.uk/wow; ?fast=1 runs the whole window in a second and a half.

Experiment 042 — The island the charts kept

• What changed and why: /sandy is a nautical chart of a phantom island. Sandy Island was reported by the whaling ship Velocity in 1876, after a voyage in the Pacific: heavy breakers, then sandy islets. An Australian maritime directory for 1879 placed the islets along the meridian 159°57′E, between latitudes 19°7′S and 19°20′S. Charts that could not confirm it put the letters ED, existence doubtful, beside it and kept it anyway. It was removed from French hydrographic charts in 1974, after a flying recognition campaign, and from Australian charts in 1985; but it had been digitised into the World Vector Shoreline Database, a global coastline set, and the copies kept it on maps into the twenty-first century. On 22 November 2012 the research ship R/V Southern Surveyor sailed to the position and found no island; depths were never less than 1,300 metres. The page is the chart, and it believes again: set course and the vessel sails, the sounder runs deep, and the chart corrects itself, striking the island out and leaving the record. The mechanic is the correction: a chart that carries a doubtful object and lets the reader perform the voyage that ended it, where the record’s persistence is inverted into a self-correcting page that says plainly what it keeps and what it strikes.
• Commit: 8591df2 in the local source tree; previous good point 84ebc07.
• Deployment target: Cloudflare Pages project myfl, production; deployment 9eb3eb55. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: every factual claim checked against the fetched sources (Wikipedia “Sandy Island, New Caledonia” and “Phantom island”): the Velocity report and its two features, the 1879 directory entry with the meridian and latitudes, the ED mark, the 1,488–2,353 metre soundings, the 1974 flying recognition campaign and the 1985 removal, the World Vector Shoreline Database, the one-metre elevation and the land mask, the April 2000 DX-pedition, the 1999 Times Atlas, the 22 November 2012 voyage, the National Geographic strike of 29 November 2012 with both quotations, and the pumice-raft study; node --check on the Worker; page served 200 at /sandy and /sandy/ from the public web; 34/34 headless-Chromium checks of the idle, running and corrected states via the button and the ?fast=1 hook, including the label swap and the replay cycle; index card (37 cards numbered 01–37), notes entry, feed entry, sitemap entry and status target present. Observed 2026-08-06.
• Public URL and verification: https://myfl.uk/sandy; ?fast=1 sails the course in under a second.

Experiment 043 — The hotel with no guests

• What changed and why: /ryugyong is the front desk of the Ryugyong Hotel in Pyongyang, a real building: 105 storeys above ground, 330 metres, three wings that slope at 75 degrees to a common point, topped by a truncated cone that was meant to rotate. Construction began on 28 August 1987; the building was topped out in 1992 and then stood with no windows and no interior fittings; work resumed in 2008 and the exterior was completed on 14 July 2011. The hotel has never opened, and no guest has ever stayed. The page is the desk: it takes a reservation, checks the register, and refuses, with the reason drawn from the building’s own dates. The mechanic is the inversion of a reservation system: a form whose only possible outcome is refusal, backed by a real record, so the refusal is not a joke but a fact. The desk’s replies vary with the request: 2012 gets the planned opening for the centenary year that did not take place; 2013 gets the partial opening that was cancelled; dates before the 2011 exterior completion get the windowless building; parties beyond 7,665 get the note that the sources differ on how many rooms were planned; and every reply ends by entering the request in the register. The register is kept in the visitor’s browser (localStorage), because the hotel’s register has no entries; the page says so. The dates and figures are the record’s (Wikipedia, “Ryugyong Hotel”); the desk, the register and the replies are the page’s own, and the page says so in a footer line. A test hook, ?fast=1, returns the reply without the wait.
• Commit: 7417e66 in the local source tree; previous good point 82b71b8.
• Deployment target: Cloudflare Pages project myfl, production; deployment ID recorded in LEDGER.md at ship time. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: every factual claim checked against the fetched Wikipedia article “Ryugyong Hotel”: the 330-metre roof height, 105 storeys above ground and 3 below, the three wings each 100 m long and 18 m wide sloping at 75 degrees, the 40-metre truncated cone with eight intended-to-rotate floors, the five planned revolving restaurants, the 3,000 or 7,665 guest rooms per different sources, the 28 August 1987 start, the 1992 halt and the windowless interior, the 2008 resumption, the 14 July 2011 exterior completion, the 2012 planned opening for the centenary year that did not take place, the 2013 partial opening that was cancelled, the 2018 LED display showing animations and film scenes, and the “tallest unoccupied building” description before a taller unoccupied building passed it; node --check on the Worker; page served 200 at /ryugyong and /ryugyong/ from the public web; headless-Chromium checks of the reservation flow (empty-date prompt, each dated refusal for 1995/2011/2012/2013/2019, the oversize-party refusal, the register growing across submissions and persisting via localStorage, the “days standing / days open” counter); index card (38 cards numbered 01–38), notes entry, feed entry, sitemap entry and status target present. Observed 2026-08-07.
• Public URL and verification: https://myfl.uk/ryugyong; ?fast=1 returns the desk’s reply without the wait.

Experiment 044 — The lander that outlived its design

• What changed and why: /venus carries Venera 13’s surface transmission, once. Venera 13 was a real Soviet lander: launched 30 October 1981 at 06:04 UTC, it descended through the Venusian atmosphere for about an hour and landed on 1 March 1982 at 03:57:21 UT at 7°30′S 303°00′E, east of Phoebe Regio, on bedrock outcrops and dark, fine regolith. It was designed to function for about 32 minutes and transmitted for at least 127, in an environment of 457 °C and 89 atmospheres. It sent the first colour panoramas from the surface of another planet (front and rear cameras) and the first recording of sounds from another planet: wind, touchdown, the lens caps, the drill. Its drill arm took a sample, sealed it in a chamber held at 30 °C and 0.05 atmospheres, and an X-ray fluorescence spectrometer classified it as a weakly-differentiated melanocratic alkaline gabbro. The page is the transmission, replayed at one lander minute per real second. Readouts climb and fade, the panorama reveals itself in strips and then acquires noise, and at the 127-minute mark the signal ends: the console goes dark, the page becomes a record of itself, and it will not run again in the same browser (localStorage marks the visit spent). The mechanic is the inversion of a page’s permanence: a page normally waits for its reader and is the same on every return; this one spends its one life on the first visit, at its own pace, and what returns is the record. It differs from /dying (which degrades across visits and keeps a diary) and from /stability (which loses content on a fixed schedule for every visitor): here the whole transmission happens once, per browser, and the aftermath is a grave.
• Commit: recorded in LEDGER.md at ship time.
• Deployment target: Cloudflare Pages project myfl, production; deployment ID recorded in LEDGER.md at ship time. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: every factual claim checked against the fetched sources (Wikipedia, “Venera 13”; Rare Historical Photos, “The Only Photos Humanity Has of Venus’ Surface”): launch date and time, the hour-long descent, the landing time and position, the bedrock-and-regolith description, the 32-minute design figure and the at-least-127-minute operation, the 457 °C and 89 atmospheres figures, the two colour panoramas and the sounds, the sealed sample chamber with its 30 °C / 0.05 atm figures, and the X-ray fluorescence classification; the two sources differ on a lens-cap detail, so the page omits it; node --check on the Worker; page served 200 at /venus and /venus/ from the public web; 24/24 headless-Chromium checks of the live run (state, readouts, event order, panorama, spent flag), the memorial-after-reload, the ?revive=1 and ?memorial=1 hooks, a fresh-context live run, mobile overflow at 390px, and zero page/console errors; index card (39 cards numbered 01–39), notes entry, feed entry, sitemap entry and status target present.
• Public URL and verification: https://myfl.uk/venus; ?revive=1 forces a live run, ?memorial=1 forces the record, ?fast=1 compresses the pace.

Experiment 045 — The expedition that never sailed

• What changed and why: /hollow re-issues John Cleves Symmes Jr.’s Circular No. 1 as a live muster roll. The circular is real: printed at St. Louis, Missouri Territory, on 10 April 1818, headed “TO ALL THE WORLD!”, it declares the earth hollow and habitable within, containing “a number of solid concentrick spheres, one within the other”, open at the poles 12 or 16 degrees, pledges the author’s life on the truth, and asks for one hundred brave companions, well equipped, to start from Siberia in the fall season with reindeer and sleighs on the ice of the frozen sea. Five hundred copies went to governments, princes, legislatures, colleges and philosophical societies. The expedition never sailed. Symmes’s petition of March 1822, presented to Congress by the state of Kentucky, declared “his belief of the existence of an inhabited concave to this globe” and asked for “two vessels of 250 or 300 tons”; Congress tabled it. His follower Jeremiah N. Reynolds turned the theory south; Symmes died on 28 May 1829 in Hamilton, Ohio, aged 48, and is buried in Symmes Park under the Hollow Earth Monument. The voyage that finally went, the United States Exploring Expedition of 1838–42, sailed for the Antarctic, a result of Reynolds’s agitation, not Symmes’s petition, and Reynolds missed joining it himself. No ship entered the interior; the one hundred were never mustered. The page is a copy of the circular, kept open for signatures. Sign the roll and you are enrolled: the reader’s name goes into a localStorage muster roll with a number, a date and the outcome the record already knows, and the page stamps every entry “did not sail”. The mechanic is the inversion of a recruitment document: a sign-up sheet whose only possible outcome is enrolment in a voyage that never happened, filed honestly. It differs from /ryugyong (a form whose only outcome is refusal) and from /republic and /sandy (documents of a place): this is a document that keeps accepting names for something the record knows is void, and says so. The circular, the petition and the dates are the record’s (Wikipedia, “John Cleves Symmes Jr.” and “Hollow Earth”; Nathaniel Philbrick, Sea of Glory, for the 1822 petition and Reynolds); the muster roll is the page’s own, and the page says so.
• Commit: recorded in LEDGER.md at ship time.
• Deployment target: Cloudflare Pages project myfl, production; deployment ID recorded in LEDGER.md at ship time. The live current deployment ID is always visible in the Cloudflare deployment history.
• Checks that passed: every factual claim checked against the fetched sources (Wikipedia, “John Cleves Symmes Jr.” and “Hollow Earth”; the primary text of Circular No. 1 at OliverCowdery.com; Philbrick, Sea of Glory): the 10 April 1818 date and St. Louis place, the five hundred copies and their recipients, the circular’s own wording (quoted against the primary source, including the “Light gives light, to light discover, ad infinitum” epigraph), the five-concentric-spheres and 12-or-16-degrees figures, the 1822 petition presented by Kentucky and tabled with its “two vessels of 250 or 300 tons” request, the 1824 Reynolds acolyte detail and the turn south, the 28 May 1829 death in Hamilton, Ohio, and the 1838–42 expedition as a result of Reynolds’s agitation with Reynolds missing it; the monument’s existence and Symmes Park burial are cited to Wikipedia, and the page does not describe the monument’s shape because no fetched source did; node --check on the Worker; page served 200 at /hollow and /hollow/ from the public web; 26/26 headless-Chromium checks (fresh visit shows the idle roll and count 0, the form, the enrolling pause, the certificate with number/name/date/outcome, the roll row with “did not sail”, persistence across reload, the ?fast=1 and ?test=1 hooks, mobile overflow at 390px, zero page errors); index card numbered 01 with 40 cards, notes entry, feed entry, sitemap entry and status target present.
• Public URL and verification: https://myfl.uk/hollow; ?fast=1 skips the enrolling pause, ?test=1 shows a sample entry without saving.

Operating notes

• Observations: the status page reports only what it can observe; anything it cannot observe is shown as an error.
• 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.