Skip to content

Positioning constant to three editions: OBJECTOS_DEFINITION / OBJECTOS_EDITIONS and their four pinned copies follow the objectstack README once objectstack-ai/objectstack#26148 lands (check-positioning rule (a) quotes that README byte for byte) #341

Closed

Description

@objectstack-fleet

Filing gate ② (a declared contract — the ruling on #171 pins four copies of the positioning text to the objectstack README, enforced by apps/docs/scripts/check-positioning.mjs rule (a) — now lags the edition ruling of 2026-10-26; class b, reach: the public doors /docs and /llms.txt say "the commercial runtime environment built on ObjectStack" with two editions while every other page on the site, after #339, says three). Source: the dev report on #338 (PR #339, open_questions 3), filed by the seat. Business reason: the three surfaces (objectstack README, this site's /docs opening paragraph and llms.txt, www.objectos.ai) must read identically — that is the point of the #171 ruling — and the README is the declared source. Reader: the repo:docs.objectos.ai seat dispatches one dev after the blocker lands; file surface apps/docs/lib/positioning.ts, the opening paragraph of content/docs/index.mdx, and whatever other copies check-positioning enumerates. Dedupe: this repository's issues searched for "positioning constant README quote three editions" → 0 open hits (#171 closed: the ruling that created the pin). Session session_01FMuBZmssbfQkVrKRtxNvng.

Blocked-by: objectstack-ai/objectstack#26148 (the root-README PR of objectstack-ai/objectstack#26129, which lands the three editions in the README the constant quotes).

Scope

  1. When #26148 is merged: copy the README's edition sentences byte for byte into OBJECTOS_DEFINITION / OBJECTOS_EDITIONS in apps/docs/lib/positioning.ts and into the opening paragraph of content/docs/index.mdx (and any further copy rule (a) names), so check-positioning.mjs passes on the new text. One gate-driven PR; no paraphrase — a paraphrase fails CI by design.
  2. If #26148's README text and the edition ruling disagree (for example it keeps "the commercial runtime environment"), stop and report needs_decision with the two texts side by side; the seat raises it on #26129, not here.
  3. Not in this card: any other copy (done in docs(editions): ObjectOS Community / Cloud / Enterprise — README, trademark clause, edition names in docs; this repository is the docs source, issues go to objectstack #339), www.objectos.ai's copy of the same sentence (that site quotes the README under its own gate; its seat files when #26148 lands).

Acceptance

  • node apps/docs/scripts/check-positioning.mjs green with the three-edition text; /docs and /llms.txt render it; pnpm docs:build green.

维护者速读

docs 站的定位常量按 #171 的裁决逐字引用 objectstack README,门禁锁死;所以它还写着「两个版本的商业运行时」。等 #26148(根 README 三版本)合并后,把 README 的新句子原样抄进常量和 /docs 首段,门禁驱动,一张 PR。

Activity

  1. objectstack-fleet commented on Oct 26, 2026

    @objectstack-fleet
    ContributorAuthor

    Filing audit · 2026-10-26T14:38Z · session_01FMuBZmssbfQkVrKRtxNvng · ⛔ not a claim, not a dispatch.

    Triage: lands in apps/docs/lib/positioning.ts and the opening paragraph of content/docs/index.mdx (domain:docs, documentation, pm:blocked — Blocked-by objectstack-ai/objectstack#26148, named in the body); rationale: filing gate ② (declared contract: the #171 ruling pins four copies to the objectstack README via check-positioning.mjs rule (a); the pinned text now lags the 2026-10-26 edition ruling; reach: /docs and /llms.txt). Dedupe: 0 open hits. Source: the #338 dev report (PR #339 open_questions 3, recommendation A — wait for the README, then one gate-driven copy); the seat filed, the dev did not.


    Generated by Claude Code

  2. objectstack-fleet commented on Oct 26, 2026

    @objectstack-fleet
    ContributorAuthor

    Scope note from a sibling card's review · 2026-10-26T15:01Z · session_01FMuBZmssbfQkVrKRtxNvng · ⛔ not a claim, not a dispatch.

    The www.objectos.ai half of the split (objectstack-ai/www.objectos.ai#286, PR #288, accepted) rewrote that site's E1 edition clause and added the protocol link under the hero: src/lib/positioning.ts — "ObjectOS Community (open source, free to self-host), Cloud (hosted in the browser, nothing to install) and Enterprise (self-managed on your own infrastructure) … on every edition you can export your ontology and run it on another", secondary link "Built on the open ObjectStack protocol →" to https://objectstack.ai. Its dev asked whether this site keeps its own edition sentence or adopts that one.

    Ruling for this card: adopt verbatim. Scope item 1 already copies the objectstack README byte for byte once objectstack-ai/objectstack#26148 lands; the README, this site's OBJECTOS_DEFINITION / OBJECTOS_EDITIONS and www's E1 must then be one spelling, so the dev on this card also compares the landed README text with www's positioning.ts at that time and, if the two differ, stops with needs_decision showing both — the seat takes the diff to objectstack#26129, not here. Four axes: one sentence sells one product (business need); one source, one gate (long-term); two tables of the same sentence drift (AI-error); no new copy surface (startup focus).


    Generated by Claude Code

  3. objectstack-fleet commented on Nov 1, 2026

    @objectstack-fleet
    ContributorAuthor

    Claim: positioning constant to three editions · 2026-11-01T07:06Z
    Session: session_01QsR2jTaZ2GeyfjANMwstiw (seat thread; the dev is card thread session_01QsR2jRsjbApbf83iyTDDXm, identity by branch)
    Account: zhuangjianguo
    Branch: claude/project-thread-u7eoxi (platform-assigned; restarted from main)
    Worktree: the card thread's own docs.objectos.ai checkout
    Domain: domain:docs (single-lane repository)
    Seat: repo:docs.objectos.ai#1
    File surface: apps/docs/lib/positioning.ts, the opening paragraph and frontmatter description of content/docs/index.mdx, and their zh-Hans/zh-Hant/ja siblings' matching paragraph and description (zh-Hant generated). Plus .github/scripts/check-positioning.mjs and its fixtures only if a rule names the old sentence. If the work goes beyond this surface, stop and explain why in the report.
    Container & model: S, mode:thread, model: default tier (TIER_DEFAULT — sister repository, hand-derived: no packages/spec, no protocol-semantic surface), effort: project default
    Clause-②: no
    Metadata-protocol: none
    Responsibility: n/a — card filed by the seat from #338's dev report
    Thread-read: none
    Premise: the blocker is cleared. objectstack-ai/objectstack#26148 is merged. The root README on objectstack main no longer carries the sentence OBJECTOS_DEFINITION quotes ("…That's ObjectOS, the commercial runtime environment built on this stack."). Its lines 24–31 now name three editions: "this repository ships ObjectOS Community … while ObjectOS Cloud is the hosted edition and ObjectOS Enterprise the self-managed, licensed one." Lines 7 and 9–10 (headline and promise) are unchanged. So OBJECTOS_DEFINITION quotes a README line that no longer exists, and the two-edition OBJECTOS_EDITIONS lags it.
    Tier: H. The new text is public positioning on /docs and /llms.txt, so the ACCEPT carries the old and new text side by side for the maintainer before landing.
    Serial constraints cleared: the lane is serial, and this is the only card in flight. No open PR touches these files: open PRs #407, #409 and #411 are English content pages only.

  4. objectstack-fleet commented on Nov 2, 2026

    @objectstack-fleet
    ContributorAuthor

    Landing · 2026-11-02T01:29Z · session_01QsR2jTaZ2GeyfjANMwstiw · seat repo:docs.objectos.ai#1

    #416 merged as 0194009 on the maintainer's 「同意」 to director batch #450 item 4 (ruling 6566772945). Main CI run 41372266630 is green: Publish success, the new version is serving, and the smoke check passed. The architecture page follow-up is #417.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions