Resolve packs from their repositories and installed packages

Status: Accepted. Date: 2026-09-30. Card t_ad153e0a, tasks t_9434ffbc and t_3ba9c176.

Company decision 0030 made twin-world a platform repository without packs. The carried runtime and website still resolve vendors through the removed platform catalog tree. The website also imports index, scorecard and grade scripts that were not carried into this repository.

A checkout catalog takes a pack repository root, with one vendor package directly under it. A World rooted in a twin-world checkout discovers the sibling twin-packs-p3 repository and merges it with installed packages, preserving the existing preference for the derived pack and then the higher major version. Application Worlds discover their installed packages. Init records selected checkout paths relative to the World root or installed package names; pinning, native frontends and asset reads resolve the same vendor package. Directory discovery performs no work at module import.

The website lists these packages and their lanes, reads the current generated demand scan and committed grades, and links vendor source to twin-packs-p3. Missing grade and maintenance evidence remains absent. Building a page does not grade a pack or import its implementation. Cloud builds declare checkout packs as file dependencies or use the catalog index's published versions.

The facts compiler reads current descriptors and explicitly declared real-server backings. It does not retain an absent vendor's facts from an older generated artifact. A backing has adoption and endpoint facts from its own declaration, and claims no pack protocol or exported factory. LiveKit's server declaration and its facts share world-runtime/src/backings.ts; the demand scan retains identities for vendors awaiting a pack.

The architecture's catalog section owns the contract. This implements decision 0030 within the existing catalog interface; it adds neither a second catalog nor a new orchestration mechanism. Automated checks and person walks are deferred by the owning card's build instructions.