Download
Download
Source visibility, future release packages, future account/release eligibility and runtime authorization are separate concerns here.
Download keeps public source / clone posture separate from packaged release access, future account-side release eligibility and runtime-side authorization. No artifact name, version, checksum, release date or repository URL is invented here.
Catalog
Release access by product
| Product | Role | Source / clone posture | Release package posture | Account / release eligibility | Runtime authorization |
|---|---|---|---|---|---|
| Runtime / System | Core governed runtime | Visible from source where public repositories are configured. No per-product clone URL is asserted here. | Future packaged runtime distribution. No installer, archive, version, release date or checksum is published in this build. | Future account and release services can later decide whether an account can access runtime releases or channels. | Running the runtime remains separately governed by account, machine, license and runtime gate decisions. |
| CLI | Command client | Source visibility depends on configured public repositories. This page does not claim a public clone target for the CLI. | Future packaged CLI distribution. No binary name, package filename, version or checksum is published in this build. | Future release services can later determine whether a signed-in account can access CLI packages or channels. | Using the CLI against governed runtime remains separately authorized from clone or download access. |
| Loom | Visual client | Public source visibility is only described where repositories are actually configured. No Loom repository URL is invented here. | Future packaged client distribution. No installer, build identifier, version or release date is published in this build. | Future account and release services can later decide Loom release or channel access without this page claiming live eligibility. | Connecting Loom to governed runtime remains separately controlled by runtime, machine, license and gate decisions. |
| VS Code | Editor extension | Source visibility remains truthful only where a public repository exists. No extension source URL is asserted here. | Future extension distribution. No marketplace package, installer, version, release date or checksum is published in this build. | Future release services can later determine extension access without claiming live extension access now. | Extension operation against governed runtime remains separately authorized after install, not granted by package access alone. |
Model
How Download separates access
- Source / clone
- Development, inspection or build-from-source posture where public repositories are available. Public visibility does not imply packaged release access.
- Release package
- Future installer, binary or client artifact distribution. This page does not publish package names, versions, release dates, checksums or latest-release claims.
- Account / release eligibility
- Future account and release services can later decide release or channel access. No live access decision or release state is shown here.
- Runtime authorization
- Runtime and client gate checks apply separately after clone or install. Download or source access does not by itself authorize runtime operation.
Runtime / System
Core governed runtime
Local runtime surface for governed execution and sealed operation.
- Source / clone
- Visible from source where public repositories are configured. No per-product clone URL is asserted here.
- Release package
- Future packaged runtime distribution. No installer, archive, version, release date or checksum is published in this build.
- Account / release eligibility
- Future account and release services can later decide whether an account can access runtime releases or channels.
- Runtime authorization
- Running the runtime remains separately governed by account, machine, license and runtime gate decisions.
CLI
Command client
Command-line client for invoking and supervising governed runtime work.
- Source / clone
- Source visibility depends on configured public repositories. This page does not claim a public clone target for the CLI.
- Release package
- Future packaged CLI distribution. No binary name, package filename, version or checksum is published in this build.
- Account / release eligibility
- Future release services can later determine whether a signed-in account can access CLI packages or channels.
- Runtime authorization
- Using the CLI against governed runtime remains separately authorized from clone or download access.
Loom
Visual client
Visual client surface for guided governed workflows and operator interaction.
- Source / clone
- Public source visibility is only described where repositories are actually configured. No Loom repository URL is invented here.
- Release package
- Future packaged client distribution. No installer, build identifier, version or release date is published in this build.
- Account / release eligibility
- Future account and release services can later decide Loom release or channel access without this page claiming live eligibility.
- Runtime authorization
- Connecting Loom to governed runtime remains separately controlled by runtime, machine, license and gate decisions.
VS Code
Editor extension
Editor-integrated client surface for development-time interaction with the runtime.
- Source / clone
- Source visibility remains truthful only where a public repository exists. No extension source URL is asserted here.
- Release package
- Future extension distribution. No marketplace package, installer, version, release date or checksum is published in this build.
- Account / release eligibility
- Future release services can later determine extension access without claiming live extension access now.
- Runtime authorization
- Extension operation against governed runtime remains separately authorized after install, not granted by package access alone.
Future release visibility and account eligibility will come from the account/release platform later. Download or source access does not by itself authorize runtime operation.
Runtime and client operation remain governed separately by account, machine, license and runtime gate decisions. This page does not fetch or compute release eligibility, artifact state, entitlement or runtime authorization.
Use Interfaces for client surfaces, Get Started for runtime orientation, Account for create-account entry and the technical /dashboard route only after real sign-in and product-shell data exist.