Skip to content

docs: adopt the 'Ontology is the software' positioning across README, docs landing page and glossary #21574

Closed

Description

@objectstack-fleet

立卡门类别 ③ — 维护者直派的任务 (maintainer-directed task).

Maintainer ruling (verbatim, untranslated)

本体即软件,这个口号不错

创建一个issue,更新readme和相关文档

Given in session https://claude.ai/code/session_011hRnra93sK5Q2gTYYTbdJR on 2026-10-03, after a positioning discussion that settled on the three-line scheme below.

What changes

Adopt a three-line positioning. The slogan carries the stance, the descriptor carries the promise and the limiter, and today's headline becomes the developer-facing proof line.

Line 中文 English
Slogan 本体即软件。 The ontology is the software.
Descriptor 一份可执行的业务本体。AI 写,运行时跑,Agent 用,归你所有。 One executable business ontology. AI writes it, the runtime runs it, agents operate it, you own it.
Proof line (kept, demoted) 装得下,才管得住。 Apps small enough for AI to hold whole.

The slogan is the category claim: the docs already say "The Schema is the Application"; this swaps the technical word for the category word. The descriptor is what keeps the claim honest: the ontology here is an executable business ontology (objects, relations, actions, permissions, flows, agent and tool definitions), not a formal ontology in the knowledge-representation sense and not a read-only semantic layer over existing systems.

Surfaces to update (measured on main at 6dd99b8)

  1. README.md: the blockquote headline (line 7) and the two "business ontology" sentences (lines 13 and 166). Lead with slogan plus descriptor; keep the "small enough" paragraph that already follows ("The other half is size") as the proof.
  2. apps/docs/app/[lang]/page.tsx: the hero heading (around line 215), the site description constant (line 36), the "what that metadata is" paragraph (around line 297) and the closing card (around line 450). Keep the meta description in sync with the constant.
  3. content/docs/getting-started/glossary.mdx, "Business Ontology" entry: extend it into a two-way contrast, knowledge ontology (describes, read-only, reasoned over) versus executable ontology (defines the app, runs it, validated rather than reasoned). Keep the two existing bullets (you own it; it is executed). State the ontology-core versus projections split: core = objects, relations, actions, permissions, flows, agent and tool definitions; projections = views, dashboards, apps, translations, themes.
  4. content/docs/concepts/index.mdx ("The Three Truths", line 95) and content/docs/concepts/metadata-driven.mdx (section 3 "The Schema is the Application", line 142): add the one-line bridge from "the schema is the application" to "in the enterprise-AI vocabulary, the ontology is the software", and name the core versus projection split once.
  5. Any other hand-written page that restates the headline. Re-run the grep for "hold whole", "small enough" and "business ontology" over README.md, content/docs and apps/docs before opening the PR; the list above is what that grep returned at 6dd99b8.

Guardrails for the author

  • Four facts must survive in the copy; they are what keeps the word "ontology" defensible: there is no object inheritance, no axioms and no reasoner (the spec retired the abstract key under ADR-0049 for exactly this reason); it is not a semantic layer over existing systems (datasource federation is early); views, dashboards, apps and i18n are projections, not ontology; code does not disappear, it moves into the runtime (hooks, action bodies, CEL and constrained JSX remain).
  • Docs only. No spec, runtime or packages/* change. Never touch content/docs/references/** (auto-generated), content/docs/releases/** (release-owned) or packages/*/CHANGELOG.md.
  • content/blog/context-window-is-the-constraint.mdx is a dated post; leave it as is.
  • The docs build (pnpm --filter @objectstack/docs build) must stay green. No new page, so no meta.json change.
  • Changeset: nothing here publishes, so the skip-changeset label qualifies only if packages/ is untouched; verify before applying it.

Non-goals (follow-ups, not this card)

  • Naming the ontology core inside packages/spec (an ontology namespace or a documented subset). Separate spec-lane card if the maintainer wants it.
  • Carrying the slogan into the console or Studio copy. That is the objectui sibling repo.

Who acts

domain:devx lane, one os-dev dispatch via /pm-dispatch, one docs-only PR. Precedent on the same surfaces: #9241 (closed, landed by #9242) changed the README headline and the docs landing page hero together under the maintainer's 2026-08-17 tagline ruling; the 2026-10-03 ruling above supersedes that wording. Two carry-overs from #9241 still hold: the number discipline (150k always names the whole app including UI, 100k always names the business logic; never swap the nouns) applies to any retained copy, and the GitHub repository description field lives outside git, so this card ends with a reminder for the maintainer to paste the slogan and descriptor there by hand.

Duplicate check (2026-10-03, open and closed)


Generated by Claude Code

Activity

  1. added
    documentationImprovements or additions to documentation
    pm:queueReady for the PM dispatch loop
    domain:devxDomain lane — seat card indexed by label:pm:seat
    pm:dispatchedDispatched to a dev agent by /pm-dispatch
    and removed
    pm:queueReady for the PM dispatch loop
    on Oct 3, 2026
  2. objectstack-fleet commented on Oct 3, 2026

    @objectstack-fleet
    ContributorAuthor

    Claim: PM loop round 49
    Session: session_01VDtqoecgES7ScQYGbFVDRv
    Branch: claude/issue-21574-ontology-positioning (cut from origin/main 44072fc2b9)
    Worktree: objectstack-issue-21574
    Domain: domain:devx
    Seat: domain:devx#1
    File surface: the card's five surfaces, re-measured at the claim ref. The card names line numbers at 6dd99b8; at 44072fc2b9 the grep returns the same set.

    • README.md: the headline (:7) and the two "business ontology" sentences (:13, :166). Lead with the slogan plus the descriptor. Keep "The other half is size" (:157) as the proof.
    • apps/docs/app/[lang]/page.tsx: the hero (:215-217), the description constant, the metadata paragraph (:297) and the closing card (:450). Also apps/docs/lib/site.ts wherever it carries the site description or tagline the page reads. The meta description stays in sync with the constant.
    • content/docs/getting-started/glossary.mdx, "Business Ontology" (:84): the two-way contrast (knowledge ontology vs. executable ontology), the two existing bullets kept, and the core-versus-projections split.
    • content/docs/concepts/index.mdx ("The Three Truths") and content/docs/concepts/metadata-driven.mdx ("The Schema is the Application"): the one-line bridge, and the core-versus-projection split named once.
    • Any other hand-written page the card's grep turns up at write time. The four guardrail facts survive verbatim in substance: no inheritance, axioms or reasoner; not a semantic layer; projections are not ontology; code moves into the runtime. The 150k/100k number discipline from docs:主 README 与文档首页统一换用新定稿 tagline(150k 整体 + 100k 业务逻辑拆分) #9241 holds.
    • ⛔ No packages/**, content/docs/references/**, content/docs/releases/**, CHANGELOGs, or content/blog/context-window-is-the-constraint.mdx. No new page and no meta.json change.

    Stop on a breach and explain it in the report.
    Container & model: S (copy across five surfaces, one docs build), mode:subagent, model: sonnet
    Clause-②: no
    Thread-read: none
    Serial constraints cleared: board read at 2026-10-03T10:51Z. Precedent #9241 is closed. The card names no open serial partner. The dev checks for any open PR on README.md or apps/docs/app/[lang]/page.tsx at write time.

    Priority rule 3 reading: domain:devx has no open P0/P1, and this is a category-③ maintainer-directed card, verbatim ruling on the card. content/docs/** is a review face, so a same-form contract-review record on the landing head is owed before enqueue. The GitHub repository description field lives outside git; the landing record carries the card's reminder for the maintainer.


    Generated by Claude Code

  3. objectstack-fleet commented on Oct 3, 2026

    @objectstack-fleet
    ContributorAuthor

    Triage: grade completed — priority:p2 · area:devpath. Everything else stands as filed

    Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-03T10:54Z. ⛔ Not a claim, ⛔ not a dispatch.

    • The card is the maintainer's own direction. It quotes 「本体即软件,这个口号不错」 and 「创建一个issue,更新readme和相关文档」, so it was filed already routed (documentation · domain:devx), and it is now claimed. It lacked only a priority, and triage adds p2 and area:devpath.
    • Why p2: it is the public positioning on the README and the docs landing page, and nothing is broken without it.
    • One note for the claim: the governed-surface check decides whether any listed surface is Tier H. If one is, it lands through that route.

    Generated by Claude Code

  4. added
    area:devpathThe road — create, dev, verify, publish/install, connect an agent, iterate
    on Oct 3, 2026
  5. objectstack-fleet commented on Oct 3, 2026

    @objectstack-fleet
    ContributorAuthor

    os-dev-report

    {
     "issue": 21574,
     "status": "done",
     "branch": "claude/issue-21574-ontology-positioning",
     "pr": "https://github.com/objectstack-ai/objectstack/pull/21579",
     "session": "session_01VDtqoecgES7ScQYGbFVDRv",
     "premise_still_valid": true,
     "summary": "Adopted the three-line positioning on README.md, apps/docs landing page (HOME_DESCRIPTION feeds all meta), glossary Business Ontology (two-way contrast + core/projections), and the concepts index and metadata-driven bridges. Four guardrail facts are in the copy. No open PR touched the surfaces; site.ts has no description; docs app is English-only; no README.zh exists.",
     "tests": "pnpm --filter @objectstack/docs build exit 0 (VERDICT command-exit 0); docs/README gates incl. doc-anchors, doc-authoring, single-h1, transcript-drift (after building lint closure), published-readme-links, nul-bytes, doc-formula-expressions, doc-security-posture all exit 0. head d534e8ebe0. No changeset owed (packages untouched).",
     "mcp_calls": "2 reads (issue_read get, get_comments)",
     "api_writes": "2 via fleet-write relay: pr_create (PR 21579), this comment; plus git push",
     "open_questions": [],
     "out_of_scope_findings": [
      "class: none filed; HERO_COVER.alt in apps/docs/lib/site.ts still says 'metadata framework for AI-written apps' (image alt, noted, not filed) · carrier: none"
     ]
    }

    Generated by Claude Code

  6. objectstack-fleet commented on Oct 3, 2026

    @objectstack-fleet
    ContributorAuthor

    Landed: PR #21579 → cc645f2385, verified on origin/main by content at 2026-10-03T11:54Z.

    • The five copy surfaces on main are blob-identical to the landing head 2c01a4473b:
      • README.md a504cba87e
      • apps/docs/app/[lang]/page.tsx 2c88bdcd05
      • content/docs/getting-started/glossary.mdx 36397da00e
      • content/docs/concepts/index.mdx 19b7e11d0f
      • content/docs/concepts/metadata-driven.mdx c0a7d1a6d0
    • The slogan "The ontology is the software." / 本体即软件。 and the descriptor now lead the README and the docs landing hero. HOME_DESCRIPTION drives the meta, OG, Twitter and JSON-LD descriptions. "Apps small enough for AI to hold whole." stays as the proof line.
    • The glossary "Business Ontology" entry now contrasts a knowledge ontology with an executable ontology and names the core-versus-projections split. Both concepts pages carry the one-line bridge.
    • The four guardrail facts all survive in the copy: no inheritance, axioms or reasoner; not a semantic layer; projections are not ontology; code moves into the runtime. No 150k/100k figure is in the touched copy.
    • One rework round: the first head said themes were a metadata-authored projection. Stack themes was retired at protocol 18 (packages/spec/src/migrations/entries/semantic/18.stack-themes-carrier-retired.ts), so "themes" was dropped from that sentence.
    • Changeset: none. This is copy only and packages/** is untouched, so the PR carries skip-changeset.

    Contract review (review faces: content/docs/**): FAIL on d534e8ebe0 (5968644063), then PASS on landing head 2c01a4473b. CI was green, including Build Docs.

    For the maintainer, by hand: the GitHub repository description lives outside git. Please paste the slogan and descriptor there: "The ontology is the software. One executable business ontology. AI writes it, the runtime runs it, agents operate it, you own it."

    Open neighbour, not filed: content/docs/getting-started/glossary.mdx:39 (the UI Protocol entry, pre-existing) still lists Themes, a surface retired at protocol 18. It is outside this card. A docs-accuracy card is triage's call.

    pm:dispatched removed.

    Seat domain:devx#1 · session_01VDtqoecgES7ScQYGbFVDRv


    Generated by Claude Code

  7. added a commit that references this issue on Oct 7, 2026
    cc645f2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratedocumentationImprovements or additions to documentationdomain:devxDomain lane — seat card indexed by label:pm:seatpriority:p2Medium: important, M3

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions