Link and service audit: external URLs and off-repo software need human verification

Comienza con las URL críticas para el onboarding en content/get-on-urbit.md y content/user-manual/running/cloud-hosting.md; después, comprueba los enlaces referenciados de bridge, invite, group, service, software, repository y media. Compara la UI, los comandos, los hosts y los archivos citados que aparecen en la documentación con el comportamiento actual en producción y con los repositorios externos referenciados. Se considera terminado cuando cada dependencia enumerada tiene un resultado de verificación registrado y se han identificado todos los cambios de documentación confirmados.

This came out of a documentation audit against urbit/urbit@08026c84b2 and urbit/vere@92847eb3fd, whose code-verifiable findings are in PRs #266–#281.

Everything below is the part that could not be checked from source, because it depends on the live network or on repos outside urbit/urbit. None of it is asserted as broken — it is a work list, ranked by how much damage a dead link does. File paths and counts were re-verified against master today.

---

A. Onboarding-critical — check these first

1. https://urbit.org/install/{macos-aarch64,macos-x86_64,linux-x86_64,linux-aarch64}/latest
content/get-on-urbit.md:139,147,155,163 and content/user-manual/running/cloud-hosting.md:168

These four curl commands are the entry point to the entire documentation set. Worth noting: upstream's own tooling uses a different host. pkg/arvo/ted/runtime-version.hoon:32 fetches https://bootstrap.urbit.org/vere/{pace}/last, and ted/azimuth/load.hoon:10 uses https://bootstrap.urbit.org/mainnet.azimuth-snapshot. If urbit.org/install/... no longer resolves or no longer serves a current binary, nobody can complete step 3 of get-on-urbit.md — and the docs would be pointing at a different host than the runtime does. Highest-priority check here.

2. https://bridge.urbit.org — 27 occurrences across 13 files, in get-on-urbit.md and content/user-manual/id/**.
Every keyfile-retrieval path routes through it. Needs more than a liveness check: the docs walk through specific UI ("OS" section, "Download Keyfile", Master Ticket login) that may have moved.

3. https://join.tlon.io/0v3.r87kb.fjpft.3k7b5.pbsr5.5em17 — get-on-urbit.md:26.
A hardcoded invite code, offered as the recommended fast path. Invite codes expire.

4. ~halbex-palheb/uf-public — get-on-urbit.md:333.
The group a new user is told to join first. Is the ship up and the group still under that name?

B. Services the docs depend on operationally

5. http://eth-mainnet.urbit.org:8545 — dojo-tools.md, ship-troubleshooting.md.
Still the hardcoded default in source too: app/azimuth.hoon:133,251, app/claz.hoon:14, app/eth-sender.hoon:258, sys/vane/jael.hoon:310. So docs match source — but if the endpoint is dead, both are wrong and %azimuth cannot sync out of the box. That would be an upstream bug, not just a docs fix.

6. Tlon's default L2 roller — assumed throughout content/urbit-id/l2/** and user-manual/id/**. Still operated? Still free?

7. Infura — roller-tutorial.md:33,47,92. Rebranded to MetaMask Developer; free-tier terms changed. The docs claim the free tier is sufficient and describe a Settings→ENDPOINTS UI path.

(The Goerli endpoint hardcoded in gen/roller/goerli.hoon is covered by #274, which documents the testnet path as unmaintained upstream.)

C. Planet markets and ID services

• https://azimuth.shop, https://store.pocwet.com — get-on-urbit.md:65-66. The only two purchase routes offered besides OpenSea.
• https://opensea.io/collection/urbit-id, /urbit-id-planet, /urbit-id-star — collection slugs change.
• https://urbit.live, https://urbit.me, https://lanlyd.net/ — third-party ID/analytics services in content/urbit-id/**.
• https://your-urbit.arvo.network — cloud-hosting.md. arvo.network was a legacy hosting domain; likely dead as an example hostname.

D. Software that may no longer ship — please confirm rather than assume

These I can report from source, but the conclusion needs someone who knows Tlon's repos:

8. %docket and %treaty — userspace/dist/docket.md, glob.md, software-distribution.md, app-school-full-stack/8-desk.md.
Verified: no docket or treaty agent exists anywhere in pkg/arvo/app/ at develop. pkg/landscape/{lib,mar,sur}/docket*.hoon survive, but pkg/landscape/ is frozen Landscape-1.0 code and its desk.bill does not start %docket. These presumably live in tloncorp/landscape now. Do :treaty|publish, the %docket glob-await behaviour, and the Globulator at /docket/upload still work as documented?

9. |cp /=landscape=/mar/docket-0/hoon ... — software-distribution.md:85-87.
This walkthrough boots a fake ~zod and copies files out of a %landscape desk. gen/pill/solid.hoon defaults to [%base]~ and %landscape is not a desk in pkg/arvo, so whether a fakeship has it depends entirely on which bootstrap pill -F pulls down. Someone should run this end to end on a fresh fakeship — if %landscape is absent, the flagship app-distribution tutorial breaks from step 4 onward.

10. %hark-store — userspace/examples/ahoy.md:19. Notifications in that tutorial go through it; it exists only under frozen pkg/landscape/.

11. %s3-store — user-manual/os/s3.md, running/minio.md. Same situation.

12. Groups / Studio / Pals — named as the canonical installed apps throughout updates.md. Are these still what a new user actually gets?

E. Third-party repos — likely low individual impact

content/build-on-urbit/tools/links.md is a link farm of 20+ community repos worth a batch check: ryjm/citadel, tinnus-napbus/{deskjam,docs-app,manx-utils}, midsum-salrux/herd, sigilante/{emissary,saloon,string}, litlep-nibbyt/john, lynko/re.hoon, R-JG/mast, stephenlacy/go-urbit, urbit/{yard,tools,create-landscape-app,nockjs,sigil-js,js-http-api}, Native-Planet/GroundSeg, manual.groundseg.app, Fang-/suite, dalten-collective/schooner, hanfel-dovned/Feature, tloncorp/{landscape,tlon-apps}.

Also github.com/urbit/support/wiki/** (4 links from ship-troubleshooting.md), and the pinned-SHA links in content/urbit-id/advanced-azimuth-tools.md:24,26,50 — those SHAs resolve but point at 2022-era code, so the cited line numbers (claz.hoon#L14, #L179, constants.js#L23) may no longer describe current behaviour.

F. Media assets

105 https://media.urbit.org/... image URLs across user-manual/**, urbit-id/**, and build-on-urbit/userspace/dist/**, under path prefixes reflecting the old urbit.org site layout (/operators/manual/os/updates/, /guides/additional/dist/, /site/getting-started/). If the CDN was reorganised during the site migration, large parts of the manual lose their screenshots silently — no build error, just missing images.

---

Counts and paths above were re-verified against master today; the original audit undercounted bridge.urbit.org (27, not 21) and media.urbit.org (105, not ~30).

🤖 Generated with Claude Code