[zhuangjianguo]

Requested by Steedos · project thread

Fixes #425
Ruling-ref: #334 comment 6568804196

Clause-②: no
Metadata-protocol: none

维护者速读

改了什么：站点和定位常量 OBJECTOS_EDITIONS（E1）不再说"现在就能把 Cloud/Enterprise 的本体导出并在开源运行时上运行"，改为"计划中"（无日期、不链内部卡）。E1 变了，所以 index.mdx 开头段落和 /llms.txt 跟着变。另有 13 句（index ×4、security、glossary ×2、why ×3、architecture、ontology）同样收窄；zh-Hans、ja 同步并重新盖章，zh-Hant 重新生成。

为什么改：#334 Q1 裁决：目前没有导出机制（objectstack#28914 才会构建），在它上线之前，该裁决取代 #171 Q2 对这一句的规定。

风险与回滚：纯文案，无代码行为变化。回滚即 revert 本 PR。保留了今天为真的事实：本体是普通的 ObjectStack 元数据、ObjectStack 是 Apache-2.0、ObjectOS Community 在你自己的机器上运行。

先看：apps/docs/lib/positioning.ts（E1 及其 docblock，POSITIONING 长度 517→550），然后下面的旧/新对照表。

两分钟验证：构建后 node .github/scripts/check-positioning.mjs（含 /llms.txt）和 --self-test 通过；grep -rnE "export it and run it|export them and run them|you can export your ontology|yours to export" content/docs/*.mdx content/docs/*/*.mdx（排除译文）在英文页面无结果。

需要你做的：无。

What changes

Every changed English sentence:

Where	Old	New
positioning.ts OBJECTOS_EDITIONS (E1), so also index.mdx lede and /llms.txt	On either ObjectOS Cloud or ObjectOS Enterprise, you can export your ontology and run it on the open-source ObjectStack runtime.	Your ontology is ordinary ObjectStack metadata. Exporting it from ObjectOS Cloud or ObjectOS Enterprise to run on the open-source ObjectStack runtime is planned.
index.mdx table, Retool / Appsmith	built on open-source ObjectStack (Apache-2.0), so the ontology is yours to export	the ontology is ordinary metadata for open-source ObjectStack (Apache-2.0), with export to that runtime planned
index.mdx table, Supabase / Firebase	but the definition is yours: export it and run it on the open ObjectStack runtime, or run ObjectOS Enterprise on your own database	but the definition is yours: run ObjectOS Enterprise on your own database, or ObjectOS Community on your own machine; export from ObjectOS Cloud to the open ObjectStack runtime is planned
index.mdx table, Salesforce / NetSuite	the definition is an open ontology that AI writes, agents operate, and you can export to the Apache-2.0 runtime	the definition is an open ontology that AI writes and agents operate, as ordinary metadata for the Apache-2.0 ObjectStack runtime, with export to it planned
index.mdx "On either edition, the ontology"	…are ordinary ObjectStack metadata, and you can export them and run them on the open-source ObjectStack runtime.	…are ordinary ObjectStack metadata, and exporting them to run on the open-source ObjectStack runtime is planned.
reference/security.mdx Data residency	…and on either edition your ontology is exportable to the open-source ObjectStack runtime.	…and on either edition your ontology is ordinary ObjectStack metadata; exporting it to the open-source ObjectStack runtime is planned.
resources/glossary.mdx Business ontology	It is yours on either ObjectOS edition: export it and run it on the open-source ObjectStack runtime.	It is yours on either ObjectOS edition: it is ordinary ObjectStack metadata, and exporting it to run on the open-source ObjectStack runtime is planned.
resources/glossary.mdx ObjectOS	Cloud and Enterprise are priced per AI seat, and on any edition you can export your ontology and run it on the open runtime.	Cloud and Enterprise are priced per AI seat; exporting a Cloud or Enterprise ontology to run on the open runtime is planned.
why.mdx "You own it."	…metadata, Apache-2.0, and on either edition you can export it and run it on that open-source runtime.	…metadata, Apache-2.0, and exporting it from either edition to run on that open-source runtime is planned.
why.mdx vs. Supabase, Vendor lock-in	The ontology exports to the open-source ObjectStack runtime; every layer is a plugin	The ontology is ordinary ObjectStack metadata, with export to the open-source runtime planned; every layer is a plugin
why.mdx vs. Salesforce, Data model	Objects, fields and relations in one open ontology — exportable, and runnable on the Apache-2.0 ObjectStack runtime	Objects, fields and relations in one open ontology — ordinary metadata for the Apache-2.0 ObjectStack runtime, with export planned
architecture.mdx	…and on either edition the ontology itself is yours: export it and run it on the open-source ObjectStack runtime.	…and on either edition the ontology itself is ordinary ObjectStack metadata; exporting it to run on the open-source ObjectStack runtime is planned.
ontology.mdx	On either edition the ontology is yours: it is ordinary ObjectStack metadata, and you can export it and run it on the open-source ObjectStack runtime.	On either edition the ontology is yours: it is ordinary ObjectStack metadata, and exporting it to run on the open-source ObjectStack runtime is planned.

Also:

• E1's docblock now says the clause is fixed by [Decision] Five facts about the ObjectOS image that the docs cannot state from public sources: ontology export, scheduled-work default, the os migrate entry point, JWT key rotation, and the template catalog #334 Q1, which supersedes [Decision] What does docs.objectos.ai target — the root URL is a redirect, the index title is "ObjectOS | ObjectOS", and the brand is spelled three ways #171 Q2 until the mechanism ships. The POSITIONING_SHORT docblock's length note moves from 517 to 550.
• The index opening paragraph is re-wrapped so it still equals POSITIONING.
• Table rows keep their column counts.
• The zh-Hans and ja siblings of all six pages carry the same narrowing and are restamped. zh-Hant is regenerated (6 files).
• Not changed: no export.mdx, no objectstack README, no check-positioning.mjs change (no rule pins the old E1's words; rule (a) composes the constants).

Tests

• pnpm build passes.
• check-positioning passes after the build ("4 copies equal their constants…", including /llms.txt), and --self-test passes. The built /llms.txt > line ends with the new E1.
• check-translations: zh-Hans 0/0/0, ja 0/0/0.
• check-translation-output --files (25-file list) passes with no findings.
• gen-zh-hant --check: 115 files match.
• check-locale-surface, check-search-locales, turbo run type-check and turbo run test pass.
• Sweep: no English page under content/docs matches export it and run it|export them and run them|you can export your ontology|yours to export. The word "exportable" is left on three pages where it means data export, not the ontology: resources/changelog.mdx 289 (an object exportable by nobody), cloud/plans-and-seats.mdx 133 and cloud/storage-and-limits.mdx 49 (files stay readable and exportable after a downgrade).

Acceptance notes

• Every claim says "planned", with no date and no link to objectstack#28914.
• The true facts stay: the ontology is ordinary ObjectStack metadata, ObjectStack is Apache-2.0, and ObjectOS Community runs on your own machine. The definition sentence already says Community is free and self-hosted, so E1 does not repeat it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QsR2jRsjbApbf83iyTDDXm

[objectstack-fleet]

席位核对 · ACCEPT · 2026-11-02T05:00Z · session_01QsR2jTaZ2GeyfjANMwstiw · seat repo:docs.objectos.ai#1

Ruling-ref: #334 comment 6568804196 (Q1 → B, with its erratum: E1 changes in this repository, no objectstack README PR).

1. Shape. Draft PR against main e4c31ff, head 09e9078 (23375c4 plus a content-free ours-merge of the old branch head). 25 files, +99/−96: positioning.ts, and six pages with their zh-Hans, zh-Hant and ja siblings. The body says Fixes #425. Nothing is outside the claimed surface.

2. The positioning constant, old and new.

   	OBJECTOS_EDITIONS (E1), in /docs's opening paragraph and /llms.txt
   old	On either ObjectOS Cloud or ObjectOS Enterprise, you can export your ontology and run it on the open-source ObjectStack runtime.
   new	Your ontology is ordinary ObjectStack metadata. Exporting it from ObjectOS Cloud or ObjectOS Enterprise to run on the open-source ObjectStack runtime is planned.

   The docblock now cites [Decision] Five facts about the ObjectOS image that the docs cannot state from public sources: ontology export, scheduled-work default, the os migrate entry point, JWT key rotation, and the template catalog #334 Q1, which supersedes [Decision] What does docs.objectos.ai target — the root URL is a redirect, the index title is "ObjectOS | ObjectOS", and the brand is spelled three ways #171 Q2 until objectstack#28914 ships.

3. The other 13 sentences (old/new table in the PR body). Each "you can export / exportable / exports to" now says the export is planned, with no date and no card link. What is true today is kept: ordinary ObjectStack metadata, Apache-2.0, and Enterprise on your own database. The Supabase row adds ObjectOS Community on your own machine.

4. Seat sweep. No English page still says you can export the ontology and run it on the open runtime today. The three remaining uses of "exportable" are about data or files after a downgrade (changelog 289, plans-and-seats 133, storage-and-limits 49), not the ontology, so they are out of scope.

5. Structure. Heading counts match across en, zh-Hans and ja on all six pages: index 7, security 19, glossary 42, why 10, architecture 8, ontology 5. Fenced code is byte-identical across the three.

6. Gates, seat re-run at 09e9078.

   • check-translations: zh-Hans 0/0 and ja 0/0.
   • check-translation-output --files with a list file: blocking on 18, no findings.
   • check-positioning --self-test passes. build runs the full gate, /llms.txt included.
   • Check-runs: build success · Ownership & freshness success · Node floor success.

7. Landing. Tier none. This executes a maintainer ruling on these exact sentences, and it lands through the merge queue under the standing go-ahead. www.objectos.ai renders the same E1. The director seat is routing that edit to the www owner.