Found by the seat's site-wide audit on 2026-10-06. This needs a maintainer ruling. It changes product naming on both docs.objectos.ai and www.objectos.ai.
The conflict, measured on main @ b754364
Positioning (ruling Q1 on #171, 2026-10-05)
apps/docs/lib/positioning.ts OBJECTOS_EDITIONS reads: "ObjectOS runs hosted in the browser with nothing to install (ObjectOS Cloud) or self-managed on your own infrastructure (ObjectOS Enterprise)…"
- index, why, architecture, quickstart, faq, glossary and security follow it, and so does www's
src/lib/positioning.ts.
License & Pricing
content/docs/resources/license.mdx:8-10 and :38-44 define:
- ObjectOS Cloud: Free / Team / Business;
- ObjectOS Self-Managed: Business Self-Managed (single node, 10–25 AI seats, $540 / AI seat / yr) and Enterprise.
- The Editions table gives Enterprise as "cloud or private deployment".
deploy/index.mdx:3-6 and deploy/docker.mdx use "Self-Managed".
README.md:38 lists Enterprise only under Self-Managed.
The result: a reader cannot tell whether Business Self-Managed counts as "Enterprise", or whether Enterprise is offered on Cloud. The legal pages in #294 had to choose, and they follow E1.
Options
- A. Keep E1 as the product vocabulary. Self-managed is called ObjectOS Enterprise.
license.mdx, deploy/** and README are re-worded to match, with Business Self-Managed described as an Enterprise single-node option and the "cloud or private deployment" cell revisited. This changes how pricing is described.
- B. Keep
license.mdx as the product vocabulary. The editions are ObjectOS Cloud and ObjectOS Self-Managed (Business single-node, Enterprise). The E1 sentence changes on both sites, along with the positioning constant, the gate and about 8 pages per site.
- C. Name the deployment modes, not the editions, in positioning (recommended). E1 becomes "…hosted in the browser with nothing to install (ObjectOS Cloud) or self-managed on your own infrastructure, and either way you can export your ontology…". The "(ObjectOS Enterprise)" parenthetical goes, so the positioning makes no claim about which plan is self-managed.
license.mdx stays the single source for plan names. This is the smallest change that makes every page true under today's price list.
Recommendation: C. It touches one sentence on each site plus the pages that repeat it, and it leaves pricing to the pricing page.
After the ruling
The seat records it here (Ruled: line in the body). Execution goes to the docs on-ramp card filed with this one, and to the www copy sweep card.
Generated by Claude Code
Found by the seat's site-wide audit on 2026-10-06. This needs a maintainer ruling. It changes product naming on both docs.objectos.ai and www.objectos.ai.
The conflict, measured on
main@b754364Positioning (ruling Q1 on #171, 2026-10-05)
apps/docs/lib/positioning.tsOBJECTOS_EDITIONSreads: "ObjectOS runs hosted in the browser with nothing to install (ObjectOS Cloud) or self-managed on your own infrastructure (ObjectOS Enterprise)…"src/lib/positioning.ts.License & Pricing
content/docs/resources/license.mdx:8-10and:38-44define:deploy/index.mdx:3-6anddeploy/docker.mdxuse "Self-Managed".README.md:38lists Enterprise only under Self-Managed.The result: a reader cannot tell whether Business Self-Managed counts as "Enterprise", or whether Enterprise is offered on Cloud. The legal pages in #294 had to choose, and they follow E1.
Options
license.mdx,deploy/**and README are re-worded to match, with Business Self-Managed described as an Enterprise single-node option and the "cloud or private deployment" cell revisited. This changes how pricing is described.license.mdxas the product vocabulary. The editions are ObjectOS Cloud and ObjectOS Self-Managed (Business single-node, Enterprise). The E1 sentence changes on both sites, along with the positioning constant, the gate and about 8 pages per site.license.mdxstays the single source for plan names. This is the smallest change that makes every page true under today's price list.Recommendation: C. It touches one sentence on each site plus the pages that repeat it, and it leaves pricing to the pricing page.
After the ruling
The seat records it here (
Ruled:line in the body). Execution goes to the docs on-ramp card filed with this one, and to the www copy sweep card.Generated by Claude Code