From 01883c75bf9b6d379f9a2515db13e76f86583047 Mon Sep 17 00:00:00 2001 From: os-bill Date: Wed, 2 Sep 2026 15:42:10 +0000 Subject: [PATCH 1/2] docs: scope "the runtime image" to ObjectOS where the claim depends on it The bare phrase names two incompatible artifacts across the corpus: the licensed commercial ObjectOS image and the Apache-2.0 ObjectStack framework image. Different licences, different distribution, different boot behaviour, so an unscoped sentence about one is not true of the other and a reader cannot tell which artifact to test it against. Applies the convention already in use at reference/cli.mdx and resources/license.mdx to the two sites where the phrase is bare AND the claim is referent-dependent. Subject only; no behavioural claim is added, softened or removed. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01ChPQM8jamxLUfUAxwFpJ8S --- content/docs/deploy/air-gapped.mdx | 5 +++-- content/docs/reference/environment-variables.mdx | 2 +- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/content/docs/deploy/air-gapped.mdx b/content/docs/deploy/air-gapped.mdx index a482192..06fdc5a 100644 --- a/content/docs/deploy/air-gapped.mdx +++ b/content/docs/deploy/air-gapped.mdx @@ -81,8 +81,9 @@ with it. ## Getting the image inside the network -The runtime image lives in a private registry that a disconnected site cannot -reach, so the image crosses the boundary the way your other artefacts do. +The ObjectOS runtime image lives in a private registry that a disconnected +site cannot reach, so the image crosses the boundary the way your other +artefacts do. Do the verification on the connected side, while you still have the registry and the tooling: check the **signature**, the **SBOM** and the **build diff --git a/content/docs/reference/environment-variables.mdx b/content/docs/reference/environment-variables.mdx index e5eb336..7128404 100644 --- a/content/docs/reference/environment-variables.mdx +++ b/content/docs/reference/environment-variables.mdx @@ -156,7 +156,7 @@ they can be used. | Retired name | What to use instead | |---|---| | `OS_ARTIFACT_FILE` | `OS_ARTIFACT_URL`. Nothing in the shipped runtime reads `OS_ARTIFACT_FILE`; a deployment that sets it gets the boot it would have got with nothing set, and no error naming the mistake. A local file is `file://` on the replacement, and the replacement carries the integrity pin. | -| `OS_ARTIFACT_PATH` | `OS_ARTIFACT_URL`. **The runtime image refuses a boot that carries a non-default `OS_ARTIFACT_PATH`**, naming the replacement. Two spellings for "which artifact do I boot" is one dialect too many, and the retired one never carried an integrity pin. | +| `OS_ARTIFACT_PATH` | `OS_ARTIFACT_URL`. **The ObjectOS runtime image refuses a boot that carries a non-default `OS_ARTIFACT_PATH`**, naming the replacement. Two spellings for "which artifact do I boot" is one dialect too many, and the retired one never carried an integrity pin. | | `OS_BUSINESS_DB_URL` | `OS_DATABASE_URL`, or a datasource declared in the artifact. Nothing reads `OS_BUSINESS_DB_URL`; a deployment that sets it and nothing else has no database configured at all. | `OS_CLOUD_API_KEY` is **not** a variable a self-hosted deployment sets. It is From 38cdd9a46c936d02ebd2c1286501cb4bed9339b7 Mon Sep 17 00:00:00 2001 From: os-bill Date: Wed, 2 Sep 2026 19:48:43 +0000 Subject: [PATCH 2/2] docs: scope two more referent-dependent uses of "the runtime image" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Folds in the two sites the PM's grep sweep surfaced after the first commit, applying the same test: scope the phrase where the sentence's truth or the reader's action depends on which image is meant. - reference/runtime-capabilities.mdx:59 — "Pin the runtime image to one that includes every package" is an actionable instruction whose answer differs by image. - build/marketplace.mdx:60 — what a default catalog is pre-bundled with differs by image. English only; the seven locale siblings of each page are left to the translation pass, which reports them stale and non-blocking by design. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01ChPQM8jamxLUfUAxwFpJ8S --- content/docs/build/marketplace.mdx | 2 +- content/docs/reference/runtime-capabilities.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/build/marketplace.mdx b/content/docs/build/marketplace.mdx index 7f7d47b..5305d33 100644 --- a/content/docs/build/marketplace.mdx +++ b/content/docs/build/marketplace.mdx @@ -57,7 +57,7 @@ You ─→ ObjectOS ─→ Marketplace tab ─→ pick app ─→ Install | Catalog | Source | When to use | |---|---|---| -| **Default** | Pre-bundled with the runtime image | First-time eval, demos, offline | +| **Default** | Pre-bundled with the ObjectOS runtime image | First-time eval, demos, offline | | **ObjectStack public catalog** | Public app registry | Latest community + first-party apps | | **Private catalog** | Your own published artifacts | Internal apps you don't want public | | **Local** | Files mounted into the runtime | Air-gapped, custom builds | diff --git a/content/docs/reference/runtime-capabilities.mdx b/content/docs/reference/runtime-capabilities.mdx index d4141b8..dc14100 100644 --- a/content/docs/reference/runtime-capabilities.mdx +++ b/content/docs/reference/runtime-capabilities.mdx @@ -56,8 +56,8 @@ when an optional package is missing during development — but in 1. Treat capability warnings as deployment failures. Grep startup logs for `capability not loaded` (or your equivalent) and fail the readiness probe / rollout if any appear. -2. Pin the runtime image to one that includes every package your - artifacts declare in `requires`. +2. Pin the ObjectOS runtime image to one that includes every package + your artifacts declare in `requires`. 3. When publishing an artifact, document its `requires` list alongside it so operators can verify the matching image.