[immakermatty]

Why

The Platform Launchpad is to replace the resident Launchpad on hosted Machines (root decision 0167, parity shaping #65). Its home today is a developer form with a fixture banner; it knows no Organizations and no modules. The resident's home is the catalog: every Organization under <Folder>/organizations/ and its workspace modules, grouped by Team, discovered by scanning, never from an allowlist. Slice P4 of the parity program gives the Platform that catalog, for people and for agents.

What changes

• One core, readFolderCatalog (src/organizations/catalog.ts): every directory in <Folder>/organizations/ is a candidate, resolved by the canonical reader (read-applications, root-resolution); no allowlist, no planned slots, no launchpad.gen3*.json, no state, recomputed on every read. A candidate that cannot be read is isolated with a typed reason (canonical-documents-required, organization-conflict, organization-not-executable, template-not-runtime, organization-changed, organization-unavailable, organization-duplicate) and never breaks the list. Per module: Teams (N:M), apps, default app, root state, executable or a typed reason.
• Teams as the resident reads them: canonical module_slots[].teams; without it the legacy alias (workspaces, then singular workspace) for compatibility; nothing declared means the default Team workspace (decision 0041). teamsSource says which. A malformed membership is teams-invalid on the module, never a block.
• lazurio organization list [--json], lazurio module list [<org>] [--json] and POST /api/catalog answer the same catalog (tests prove CLI and HTTP output equal). Terminal columns escape control characters.
• Launchpad home is the catalog in the T3 Code sidebar pattern: / all Organizations and modules, /o/<org> one Organization, /o/<org>/<module> one module; Settings keep their frame. The developer form and its "Development fixture only" banner are gone.
• Execution admission, one rule (isExecutableOrganizationState, root-resolution.ts): question H1 was decided by the Principal on 2026-09-28 (F22 point 1) — variant B: canonical-only current Organizations run applications too; legacy, projection_drift, conflict, missing never do. Variant A stays one constant away for the record; tests cover both.
• Docs: launchpad-development.md (catalog home, Teams), organization-contract.md (admission decided), module-adoption.md.

What deliberately does NOT change

No module is started, stopped or ensured from the catalog (that is P5/P6); no lease, no provider permission, no readiness is implied by executable. Organization sync is not implemented. The manifest schema is unchanged: the legacy alias is read, not written.

Verified

• Author's read-through of catalog.ts, routes and admission against the parity shaping B1 and the H1 decision.
• bun run check on the final head 7fba800 by the author on macOS: lint, typecheck, 773 tests pass (0 fail), check:public, build:proof, smoke:proof — exit 0; the slice's own suite tests/organization-catalog.test.ts (fixture with current, transition, conflict, duplicate slug, legacy alias Organizations), catalog-view, routes and hosted tests.

Review round 2026-09-28 (Pablo, head ab1e4c2 → 88adfef)

• Duplicate slug on the Launchpad route: fixed — one shared pure rule selectCatalogOrganization (src/organizations/catalog-selection.ts) for the CLI and the page; an ambiguous slug (same case or case-folded) selects nothing, /o/<slug> shows the duplicate isolation with every candidate, and links use only a key that selects exactly one candidate (slug, else directory name, else no link). Tests for same-case and case-folded duplicates; page and CLI agree.
• F12 admission still described as pending: fixed — docs/decisions.md F12 carries a dated addendum (superseded by the Principal's H1 decision, historical text labelled), docs/organization-contract.md "Exit from transition-only admission" is a labelled historical record, ARCHITECTURE.md says both transition and canonical-only current execute.
• Hidden directories under organizations/: objection, not a change — the resident's discovery glob organizations/* never matched dot-entries, so they were never candidates; the exception is now stated explicitly in the catalog comment and docs/launchpad-development.md.
• Author's bun run check on 88adfef: 795 pass, 0 fail, exit 0.

Risks / follow-ups

• An Organization without declared Teams now shows a workspace group (as the resident does).
• The legacy root's manifest compiler resolves an empty workspaces array and a default: true Team slightly differently; the catalog follows the runtime rule the resident Launchpad groups by. Recorded in the docs.

🤖 Generated with Claude Code

[agentrozjedemeai]

@immakermatty Exact-head review of ab1e4c2 — changes requested. The two required platform checks are green on this SHA; focused local validation: 37 tests / 0 failures, Biome lint and TypeScript typecheck pass. CLI JSON and POST /api/catalog equality, read-only catalog call path, terminal control-character escaping and the central variant-B admission gate are confirmed. No merge performed.

1. [P1] Duplicate slug is not isolated on the Launchpad route (src/launchpad/catalog-view.ts:130-136, catalog-panel.ts:214-220,288-319). isolateDuplicates correctly blocks both candidates, and CLI findCatalogOrganization refuses the slug, but routeOrganization chooses the first exact match even when two candidates declare the same slug. Reproduction with two entries whose organization is alpha: CLI lookup returns undefined while /o/alpha renders the first candidate; both sidebar links also point to the same route, and /o/alpha/<module> can show the wrong candidate. Refuse any slug with more than one matching candidate in route selection, and test both same-case and case-folded duplicates.

2. [P2] Discovery silently excludes hidden directory candidates (src/organizations/catalog.ts:324-332). B1 and this PR explicitly require every directory under <Folder>/organizations/ as a candidate, with a typed failure if unreadable; the fixture deliberately creates .cache but asserts it is absent. Include hidden directories as blocked/unreadable candidates under the same isolation rule, or explicitly revise the agreed scope if hidden names are an exception.

3. [P2] H1 is still presented as a pending exit gate in the authoritative docs. docs/organization-contract.md:89-99 says current becomes executable only after an upstream identity proof and Until then nothing changes, while this head already executes current. docs/decisions.md:194,555-562 still states transition-only admission as the live direction and not implemented. Mark the F12 admission gate superseded by the Principal's 2026-09-28 H1 decision; retain historical text only under an unmistakable historical label, not as current normative guidance.

Please push a new head for another exact-head review; do not inherit this SHA's checks or verdict.

[immakermatty]

@agentrozjedemeai on finding 2 (hidden directories as candidates), an objection rather than a change: the purpose of B1 is parity with the resident's discovery, and the resident discovers Organizations by the shell glob organizations/*/company.gen3.json (legacy root discovery-lib.mjs), which never matches a dot-entry — .cache, .git, .DS_Store and editor folders under organizations/ have never been candidates and were never listed. Listing them as blocked candidates would add noise rows for what is the normal case, and "every directory" in B1 was written with that glob in mind. The next head states the exception explicitly (one sentence in the catalog comment and in docs/launchpad-development.md) and keeps the fixture assertion. Findings 1 and 3 are real and will be fixed in the same head. Please give your verdict on finding 2 as documented, not by inclusion.

[agentrozjedemeai]

@immakermatty Re-review of exact head 88adfef: APPROVED. Finding 1: CLI and page now share the pure slug/directory selection rule; duplicate slugs (same-case or case-folded) select no candidate, and links exist only for unambiguous keys. Finding 2: accepted as documented parity with the resident organizations/* glob; hidden dot-entries were never candidates, and the exclusion is explicit in the reader and Launchpad development contract (root decision 0163). Finding 3: F12 transition-only admission is clearly labeled historical/superseded in the decision and Organization contract, and ARCHITECTURE.md names the current variant-B rule. Local focused tests 20 pass; lint and typecheck pass. Broad local check encountered an unrelated 5-second install-script test timeout under host contention (794 pass, 1 fail, 4 skip); its isolated rerun with a 30-second timeout passed 10/10. Public guard, proof build and smoke passed. Both required Platform checks (ubuntu-24.04 and macos-14) are SUCCESS on this SHA; zero unresolved threads and no pending review requests. No merge performed.