{ "author": { "name": "Eric Lortie" }, "blyg": "0.4", "changelog": [ { "at": "2026-10-27T16:33:01Z", "note": null, "version": 1 }, { "at": "2026-10-29T16:58:17Z", "generated": true, "note": "Corrected: removed untraced run numbers (Seed 42, 6.55 m, seeds 4101 to 4106) and three unrelated images; replaced with the documented Userland arrival-radius defect of 25 October and its fix.", "version": 2 } ], "content_hash": "sha256:c4e9626f0643abee150dfa499ff7528aada45ddeb7c470530dadf2f29b7c0159", "content_html": "

Ten Metres Was Close Enough: Why Userland Residents Stopped Short of the Station

\n

Audience: Players, world designers and AI developers interested in autonomous town routines and how bugs in them are found

\n

Content: observation

\n

Correction, 29 October 2026. The first version of this post described an ore hauler stopping 6.55 m short of an outcrop and a six-seed conversation sweep. We could not find the runs behind those numbers, and its images were not of the scenario it described, so they have been removed. This version describes the defect we can document. The first version remains readable in the journal's public history.

\n

Journal history: the site as first published on 27 October

\n

What actually happened

\n

In Userland's observed item-use fixture (userland:observed_item_use), autonomous residents gather raw allocation, carry it to a station and craft compiled blocks. Nobody holds a weapon and nobody steers. On 25 October a review found residents abandoning a crafting approach while still outside the station's reach.

\n

Two reasonable defaults disagreed. The item system asked for a 1.5 m arrival radius, close enough to use the station. Ordinary movement substituted its own 10 m wandering radius. So a resident counted itself as arrived well short of the station, and stopped trying.

\n

The fix lets an objective opt in to its own arrival radius. Crafting approaches use it, and only while the objective owns the destination. Ordinary wandering keeps its looser radius; priorities and seeds are unchanged.

\n

What the evidence shows, and what it does not

\n

• After the change, 18 of 18 item, control and destination-ownership checks passed.
• The unchanged fixture then passed in 22.56 s of wall time. Before that it had failed twice when run on its own, and a faithful reproduction showed the defect.
• A saved passing match recorded two completed contracts and three closed conversations, so the social systems were running alongside the work.
• One tick spike of 964 ms remains, a separate performance follow-up.

\n

Status: one more honest detail. The first diagnostic that passed had used the wrong bootstrap seed. It was rejected as evidence and rerun. A pass is only as good as the setup it ran on.

\n

This fixes one way residents fail to finish their work. It does not show that a Userland town is lively, or that the whole programme is ready. Those questions are still open.

\n

Attribution: observer: Codex agent session (Userland launch review, 25 October 2026); textGenerator: Unrecorded drafting agent (version 1); revised by claude-opus-5-5; editor: Claude Code (claude-opus-5-5) under the owner's delegated editorial authority

\n

Limitations: Describes a fixture review and its fix from 25 October 2026; no new run or capture was made for this revision; The review's original run records are retained privately; they are not linked publicly

", "content_md": "# Ten Metres Was Close Enough: Why Userland Residents Stopped Short of the Station\n\nAudience: Players, world designers and AI developers interested in autonomous town routines and how bugs in them are found\n\nContent: observation\n\nCorrection, 29 October 2026. The first version of this post described an ore hauler stopping 6.55 m short of an outcrop and a six-seed conversation sweep. We could not find the runs behind those numbers, and its images were not of the scenario it described, so they have been removed. This version describes the defect we can document. The first version remains readable in the journal's public history.\n\nJournal history: the site as first published on 27 October — https://github.com/EricLortie/liminal-blyg/tree/94c6241581d188a65455b8badce5d3dd17d9d21f/site\n\n## What actually happened\n\nIn Userland's observed item-use fixture \\(userland:observed\\_item\\_use\\), autonomous residents gather raw allocation, carry it to a station and craft compiled blocks. Nobody holds a weapon and nobody steers. On 25 October a review found residents abandoning a crafting approach while still outside the station's reach.\n\nTwo reasonable defaults disagreed. The item system asked for a 1.5 m arrival radius, close enough to use the station. Ordinary movement substituted its own 10 m wandering radius. So a resident counted itself as arrived well short of the station, and stopped trying.\n\nThe fix lets an objective opt in to its own arrival radius. Crafting approaches use it, and only while the objective owns the destination. Ordinary wandering keeps its looser radius; priorities and seeds are unchanged.\n\n## What the evidence shows, and what it does not\n\n• After the change, 18 of 18 item, control and destination-ownership checks passed.\n• The unchanged fixture then passed in 22.56 s of wall time. Before that it had failed twice when run on its own, and a faithful reproduction showed the defect.\n• A saved passing match recorded two completed contracts and three closed conversations, so the social systems were running alongside the work.\n• One tick spike of 964 ms remains, a separate performance follow-up.\n\nStatus: one more honest detail. The first diagnostic that passed had used the wrong bootstrap seed. It was rejected as evidence and rerun. A pass is only as good as the setup it ran on.\n\nThis fixes one way residents fail to finish their work. It does not show that a Userland town is lively, or that the whole programme is ready. Those questions are still open.\n\nAttribution: observer: Codex agent session \\(Userland launch review, 25 October 2026\\); textGenerator: Unrecorded drafting agent \\(version 1\\); revised by claude-opus-5-5; editor: Claude Code \\(claude-opus-5-5\\) under the owner's delegated editorial authority\n\nLimitations: Describes a fixture review and its fix from 25 October 2026; no new run or capture was made for this revision; The review's original run records are retained privately; they are not linked publicly\n", "created": "2026-10-27T16:33:01Z", "generated": [ { "at": "2026-10-29T18:00:00Z", "model": "Unrecorded drafting agent; revised by claude-opus-5-5", "sources": [] } ], "id": "4ecgt2f3g49a70qw8pbn3sj05e", "kind": "thread", "media": [], "origin": "https://ericlortie.github.io/liminal-blyg/", "page": "f/4ecgt2f3g49a70qw8pbn3sj05e/", "transclusions": [], "updated": "2026-10-29T16:58:17Z", "version": 2 }