Repository navigation
[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
Description
Filing gate: ② — only the maintainer (the owner of the private ObjectOS image) can answer these.
Reader: the repo:objectos PM seat (objectstack-ai/objectstack#9831). When a question is answered, it files or dispatches the one-paragraph follow-up named under that question.
Dedupe: all 118 objectos issues, open and closed (REST page walk), grepped for ontology export, scheduled work, OS_AUTOMATION, os migrate, JWT, jwks, and marketplace … template.
- The open hits are [Decision] One name for the self-managed edition: "ObjectOS Enterprise" (positioning, 8 pages) vs "ObjectOS Self-Managed" with Business single-node and Enterprise under it (License & Pricing, Deploy) #295 only: it quotes E1, which says the ontology is exportable. It does not ask how.
- The closed hit is
configure/data-sources.mdxlinks to/docs/build/objects, which 404s — no page, no redirect #99, an earlier template page.
None of them asks these questions.
维护者速读
文档站这一轮的三个 PR(#331、#332、#333)把 17.0–17.7 的变化和「本体即软件」的说法都写进去了。但下面五件事,公开资料里查不到,只有 ObjectOS 镜像的实际行为能回答。PR 里都写成了"显式说明、不下断言"的保守措辞,所以不阻塞合并。你答一句,席位就把对应的页面改成确定的说法。每题都有推荐。
- Cloud 租户怎么导出本体? 定位常量 E1 和 6 个页面都说"可导出、可在开源运行时上跑",但没有一页写怎么导出。开源 CLI 没有导出命令,
os package export不存在,docs: explain ObjectOS in ontology terms, and correct four capability claims 17.7 contradicts #332 已删掉它。推荐:如果产品里已有入口,告诉我入口,我补一页"导出你的本体";如果还没有,先把"可导出"收窄成"规划中",免得文档声明了产品做不到的事。 - ObjectOS 镜像的
OS_AUTOMATION_SCHEDULED_WORK_ENABLED默认是开还是关? ObjectStack 17.5 起默认关:不设它,定时流程和打包的 cron 都不跑。推荐:告诉我镜像的实际默认值,我写成事实。 - 自管运维怎么在授权镜像上跑
os migrate和 17.3 的sys_record_share回填? 推荐:说明镜像里有没有osCLI 及其调用方式,升级页就能给出能直接执行的命令。 - 17.7 要求轮换 JWT 签名密钥,ObjectOS 上的做法是什么? 是轮换
OS_AUTH_SECRET加一次性清理,还是另有流程?推荐:给出做法,升级页写成步骤。安全步骤没有机制,最容易被跳过。 - ObjectOS 的模板市场还列不列
todo、compliance、content、contracts、procurement这几个模板? ObjectStack 17.7 已把它们下架,--template todo会被拒绝;build/templates.mdx的目录和index.mdx还在列它们。推荐:告诉我还列不列,我据此保留或删除。
你要做的:逐题回一句(例:「1 已有,在 Setup → 导出;2 开;3 镜像带 os;4 轮换 OS_AUTH_SECRET;5 都下架」)。
The questions, with what each answer unblocks
| # | Question | Where the docs stand today | Follow-up the answer unblocks |
|---|---|---|---|
| 1 | What is the ontology export mechanism on ObjectOS Cloud and Enterprise? | E1 (apps/docs/lib/positioning.ts OBJECTOS_EDITIONS) and six pages assert it, with no procedure. os package export does not exist (CLI package/ holds install/publish at 17.7.0) and #332 removes it |
A (it exists): a new content/docs/export.mdx, linked from those six pages. B (not yet): narrow the six sentences, and change E1 through the objectstack README per the #171 Q4 ruling |
| 2 | What does the ObjectOS image set OS_AUTOMATION_SCHEDULED_WORK_ENABLED to? |
#333 says it defaults off on ObjectStack 17.5+, tells operators to set it explicitly, and to confirm with os doctor |
build/automation/flows.mdx and reference/environment-variables.mdx state the image's value as fact |
| 3 | How does a self-managed operator run os migrate … and the 17.3 sys_record_share backfill against the licensed image? |
#333 names the commands and the @objectstack/plugin-sharing backfill functions, and says nothing runs them at boot |
operate/upgrade.mdx gets exact, runnable commands |
| 4 | How are the JWT signing keys (sys_jwks) rotated on ObjectOS after 17.7? |
#333 states the step as the release note does, with no mechanism | operate/upgrade.mdx 17.7 gets the procedure |
| 5 | Does the ObjectOS template marketplace still list todo, compliance, content, contracts and procurement? |
create-objectstack 17.7.0 refuses them as retired (measured, exit 1), yet build/templates.mdx:18-32, :79-87, index.mdx:43-44 and build/index.mdx:15, :46-48 still name them |
Keep the catalog, or remove the names |
Governing text: AGENTS.md (docs state what ships). For Q1 also apps/docs/lib/positioning.ts OBJECTOS_EDITIONS and the #171 rulings Q2 and Q4.
四维分析(五题同构,合并呈现)
- 实际业务需求: 五题都是真实运维或使用路径:导出 = 退出权,定时流程 = 提醒和夜间任务,升级步骤 = 自管客户每次升级都会碰到。不是投机面。
- 项目长远合理性: 文档写镜像的契约(contract-first),优于长期挂着"请自行确认"的对冲句。Q1 若尚无机制,收窄声明比留着空头承诺更可持续。
- 防 AI 犯错: 不确定的默认值会让 AI 写出"以为会跑"的定时流程,让运维 agent 自造迁移脚本。写成确定事实,结构上更难写错。
- 创业阶段不扩散: 五题都只是写清已存在的行为,零新功能面。Q1 选 B 也是收窄,不是扩张。
推荐: 逐题如实回答。Q1 若尚无机制选 B。
Generated by Claude Code
Activity