docs(link): the site leg, and the nine keys no phase row could catch (Phase 9c, the last) #247

wtclaude · 2026-09-15T10:48:03Z

wtclaude commented

2026-09-15 10:48:03 +00:00

Phase 9c is done, and with it the Asset Bridge. §16's row records what the leg actually was; §17.17 records what it found.

The site is the only repo whose checks read the platform over the API instead of describing it, so its starting state is a measurement rather than an opinion. It was red in two places:

checkFacts — ten failures, all expected. The protocol in all three independent reads, the bundle triple, and the three releases the cutover cut. moduleApi and the capability list did not move, which is §17.16's finding restated by a different mechanism: core's whole share of eight phases was a deletion.
checkReference — nine failures nobody planned for. AssetsEnabled, AssetBatchBytes, AssetBodyBatch, AssetFetchKeys, AssetScanMs, AssetPlayerDirection, AssetCreatureDirection, TreeEnabled, TreeChunkBytes all reached Bridge.cfg across phases 5, 6 and 7, and the public reference page never mentioned one of them. No phase row in this plan could have caught it — the rows name the repos a change edits, and this is a repo that only describes them.

Two corrections only prose could make:

§17.15's "five repositories" had already become a page on the site, naming website among them. Protocol 8 touched four, and core's absence is the more interesting half: what the asset plane needed, core already offered every module.
The site said the bridge has two ways in. It has three. The asset plane is a paged bulk read on the reply path, one request in flight — and it must not ride the event stream for a structural reason (every event is persisted and broadcast) rather than a throughput one.

The defect the phase found is a version pinned in a rig. seedDemo.mjs pinned protocol 4 under a careful comment explaining a module-uo debt that later phases paid. A literal written down with a good reason outlives the reason, and nothing checked it because the rig is not the product. It reads platform.json now.

Screenshots retaken against the real shard (D42 holds — no mock-ups): 1,095 portraits in 2.1 s, 67,496 names in 1.4 s, 313 item pictures in 0.8 s, all matching the 9a walk on a different database.

Site PR: RunicGateway/runicgateway.com#31.

AI-assisted: written with Claude Code (Claude Opus 5), reviewed by a human before merge.

🤖 Generated with Claude Code

https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4

Phase **9c** is done, and with it the **Asset Bridge**. §16's row records what the leg actually was; **§17.17** records what it found. The site is the only repo whose checks *read* the platform over the API instead of describing it, so its starting state is a measurement rather than an opinion. It was red in two places: - **`checkFacts` — ten failures, all expected.** The protocol in all three independent reads, the bundle triple, and the three releases the cutover cut. `moduleApi` and the capability list did **not** move, which is §17.16's finding restated by a different mechanism: core's whole share of eight phases was a deletion. - **`checkReference` — nine failures nobody planned for.** `AssetsEnabled`, `AssetBatchBytes`, `AssetBodyBatch`, `AssetFetchKeys`, `AssetScanMs`, `AssetPlayerDirection`, `AssetCreatureDirection`, `TreeEnabled`, `TreeChunkBytes` all reached `Bridge.cfg` across phases 5, 6 and 7, and the public reference page never mentioned one of them. **No phase row in this plan could have caught it** — the rows name the repos a change *edits*, and this is a repo that only *describes* them. Two corrections only prose could make: - §17.15's "five repositories" had already become a page on the site, naming `website` among them. Protocol 8 touched four, and **core's absence is the more interesting half**: what the asset plane needed, core already offered every module. - The site said the bridge has **two ways in**. It has three. The asset plane is a paged bulk read on the reply path, one request in flight — and it must not ride the event stream for a structural reason (every event is persisted and broadcast) rather than a throughput one. **The defect the phase found is a version pinned in a rig.** `seedDemo.mjs` pinned **protocol 4** under a careful comment explaining a `module-uo` debt that later phases paid. A literal written down with a good reason outlives the reason, and nothing checked it because the rig is not the product. It reads `platform.json` now. **Screenshots retaken against the real shard** (D42 holds — no mock-ups): 1,095 portraits in 2.1 s, 67,496 names in 1.4 s, 313 item pictures in 0.8 s, all matching the 9a walk on a different database. Site PR: RunicGateway/runicgateway.com#31. --- - [x] AI-assisted: written with Claude Code (Claude Opus 5), reviewed by a human before merge. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4

wtclaude added 1 commit 2026-09-15 10:48:07 +00:00

docs(link): the site leg, and the nine keys no phase row could catch (Phase 9c, the last) bc5b43e1a4

Phase 9c is done, and with it the Asset Bridge. §16's row 9c records what the leg
actually was, and §17.17 what it found.

The site is the only repo whose checks read the platform over the API instead of
describing it, so its starting state is a measurement rather than an opinion:

- `checkFacts` red in **ten** places — the protocol in all three independent reads,
  the bundle triple, and the three releases the cutover cut. `moduleApi` and the
  capability list did not move, which is §17.16's finding restated by a different
  mechanism.
- `checkReference` red in **nine nobody planned for** — every `Bridge.cfg` key phases
  5, 6 and 7 added, none of them ever mentioned on the public reference page. No phase
  row in this plan could have caught that: the rows name the repos a change edits, and
  this is a repo that only describes them.

Two corrections only prose could make: §17.15's "five repositories" had become a page
on the site that named `website` among them (protocol 8 touched four, and core's
absence is the interesting half), and the site said the bridge has two ways in when the
asset plane is a third — a paged bulk read on the reply path, which must not ride the
event stream for a structural reason rather than a throughput one.

The defect the phase found is a version pinned in a rig: `seedDemo.mjs` pinned protocol
**4** under a comment explaining a debt since paid. It reads `platform.json` now.

Screenshots retaken against the real shard (D42 holds): 1,095 portraits in 2.1 s,
67,496 names in 1.4 s, 313 item pictures in 0.8 s.

Site: RunicGateway/runicgateway.com#31.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4

whitlocktech merged commit e1f26de369 into main

2026-09-15 12:10:43 +00:00

whitlocktech deleted branch docs/asset-bridge-p9c

2026-09-15 12:10:44 +00:00

whitlocktech referenced this issue from a commit

2026-09-15 12:10:44 +00:00

Merge pull request 'docs(link): the site leg, and the nine keys no phase row could catch (Phase 9c, the last)' (#247) from docs/asset-bridge-p9c into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#247