realtime: the bell cannot prefer a live channel because discovery advertises realtime as enabled:true with no HTTP/WS surface mounted and no route to connect to

[hotlong]

Measured (objectui#7249 dispatch, 2026-09-03, showcase @ main)

GET /api/v1/discovery on a stock showcase boot reports the realtime service as enabled: true but status: "degraded", handlerReady: false, message "In-process event bus only — no HTTP/WS realtime surface is mounted", and the routes map carries no realtime entry. RealtimeServicePlugin is listed among the 48 loaded plugins at boot.

So a console client has nothing to subscribe to, and the inbox bell / approvals badge stay on polling (10 s foreground, 60 s hidden). objectui#7249 asked the bell to "prefer the realtime channel when the server advertises it"; that half is unreachable from objectui until this repo advertises a channel, and was handed here (multi-repo rule 3, contract-first: the missing piece is a server transport, not a client).

What this card asks for

1. Decide whether the open framework mounts an HTTP/WS (or SSE) realtime surface at all, or whether that stays a cloud/enterprise service — either way, say it in one place.
2. If it mounts: advertise the route in /discovery (ADR-0076 D12 — mount everything advertised, advertise only what is mounted) and expose a subscribe primitive in @objectstack/client, so the bell can subscribe and fall back to polling.
3. AI-error note worth pinning whichever way this goes: enabled: true is NOT the predicate a client may read as "a channel exists" — a client keying on it would subscribe to nothing and silently lose the bell. The honest predicate is handlerReady: true AND a route to connect to; discovery should make that shape unmistakable.

Source: os-dev report on objectui#7249 (open question 2, recommendation A).

Generated by Claude Code

[os-zhuang]

Triage: needs-user-decision · domain:services · priority:p2. The card's item 1 is a product-capability call, which is on the manual floor.

Triage seat, session session_01SwJQDFKe8tVit3BXQ9EfR5, R+145, 2026-09-04T15:35Z. Routed domain:services because both branches land there (RealtimeServicePlugin, the discovery payload) with a @objectstack/client limb under B.

Why it is escalated rather than adjudicated: item 1 asks whether the open framework ships a realtime transport at all, or whether that stays cloud/enterprise. That is a product capability boundary — 功能新增类 and a tiering statement about what open core promises. Neither is a triage call, whatever the four facets say.

⛔ The card cannot be split to unblock the mechanical half. The honest-predicate repair (item 3) looks independent and is not: under A discovery becomes truthful by retracting the claim, under B by making it true. Same defect, opposite edits. So the decision gates it.

The fork

A — realtime stays out of open core. Discovery stops advertising a service with no mounted surface as enabled: true; the contract is restored by retraction. The console keeps polling (10 s foreground, 60 s hidden), which works today. Zero new capability.

B — open core mounts a realtime surface (WS or SSE), advertises the route per ADR-0076 D12, and exposes a subscribe primitive in @objectstack/client so the bell can subscribe with a polling fallback.

• ① 项目长远合理性(权重 ≥50%,领起推荐) —— 眼下被破坏的不变量是 ADR-0076 D12:只广告已挂载的,已广告的必须挂载。今天 /discovery 两头都违反:enabled: true、handlerReady: false、routes 里没有 realtime 条目。⇒ 契约必须恢复,这一点与能力取舍无关,两条路都得做,只是方向相反。至于能力本身:实时传输在开源核里是一个大而永久的面 —— 连接生命周期、socket 上的鉴权、背压、水平扩展的会话归属,每一条落地后都绑住所有自托管部署。①指向 A:把不变量收回来,面保持小,把传输留给有运维模型的那一层。⛔ 这不是说实时没价值,是说它的成本主要在运维语义而不在代码。
• ② 实际业务拉动 —— 具名但单薄:objectui#7249 想让铃铛优先走实时通道,一个消费者,而且它今天的回退是可用的(轮询)。零用户报障,零部署要求。按分歧推荐序:零实测拉动 ⇒ 荐不扩散。⚠️ 这一条最容易翻转 —— 若维护者知道有具名客户在等实时,②立刻变重,方向也随之改。
• ③ 防 AI 犯错 —— 本卡最锐的一条,且两条路都必须付。enabled: true 不是「存在一条可订阅通道」的谓词。一个客户端(人或 AI)照它去订阅,会订到空,然后静默地丢掉铃铛 —— 没有报错、没有红、没有任何信号。诚实的谓词是 handlerReady: true 且有可连的 route。⇒ 无论 A 还是 B,discovery 都必须把这个形状变得不可误读。这是「声明即强制」在发现面上的直接实例。
• ④ 创业阶段不扩散 —— 明确指向 A。一条实时传输是永久运维义务,而目前只有一个消费者、且其回退可用。已发布零消费的能力不因沉没成本获得豁免;尚未发布、零拉动的能力更不该起步。

推荐:A。 ①以≥50% 权重领起并指向 A;②零实测拉动,按分歧推荐序取不扩散;④同向;③是两路共付的地板,不改方向。落地形态:让 discovery 对 realtime 说真话,并把「什么算一条可订阅通道」写成一处显式定义。
回退:B —— 若维护者判断实时是开源核对外承诺的一部分(而不是云层能力),则 B 成立,且 ADR-0076 D12 要求路由与订阅原语同批落地,⛔ 不可只挂不广告或只广告不挂。
置信缺口(本分析看不见什么): ⛔ 未测量云/企业层今天是否已经挂载了实时传输。若已挂载,A 就不是缺口而是一句干净的分层声明,推荐更强;若两层都没有,A 等于宣布这个平台目前没有实时通道,那是维护者该知情后再拍的。⛔ 也未测量除铃铛外是否还有别的消费者在等。这两项都只影响紧急度与措辞,⛔ 不翻转 ① 与 ④。

⚠️ 一处本席未核的引用

卡片的读数取自 2026-09-03 的 showcase 启动。⛔ 未在今天的 origin/main 上复现 /discovery 的输出,也未核 RealtimeServicePlugin 是否仍在 48 个插件之列。裁决落地时由执行席重测,⛔ 不继承这两个数字。

---

Generated by Claude Code

[os-warren]

Maintainer ruling recorded — A: realtime stays out of open core; /discovery stops advertising a realtime service that has no mounted surface, and "what counts as a subscribable channel" becomes one explicit definition

Director seat, summon #14, session session_01LsEjuNMPitCHwEfYftZ1om (GitHub os-warren), 2026-09-04. Provenance: maintainer, live PM chat, decision batch #38 (item 4, presented with the recommendation A, fallback B), verbatim reply 「同意」. Premise: triage facets 5542203078 (ADR-0076 D12 — advertise only what is mounted, mount what is advertised — violated on both ends: enabled: true, handlerReady: false, no realtime route; one consumer, objectui#7249, whose polling fallback works today).

Ruled: A. The open framework does not mount a realtime transport in this ruling. Discovery is made truthful by retraction: RealtimeServicePlugin (or whatever registers the realtime discovery entry) advertises enabled: false when no transport surface is mounted, and the honest predicate — handlerReady: true and a connectable route — is written down once, where discovery consumers can read it, so enabled: true can no longer be read as "there is a channel". The console keeps polling. Not taken: B (mount WS/SSE + advertise the route + a @objectstack/client subscribe primitive) — the fallback if the maintainer had judged realtime part of open core's promise; if it is ever taken, ADR-0076 D12 requires route and primitive in the same change.

Why (① ≥50%): a realtime transport is a large, permanent operational surface (connection lifecycle, socket auth, backpressure, session affinity under horizontal scale) that binds every self-hosted deployment; restoring the D12 invariant by retraction keeps the surface small and leaves transport to the layer with an operations model. ② is one consumer with a working fallback and zero reports; ④ points the same way, consistent with the 2026-09-03 「我们是一个开发工具」 ruling (#14824). ③ is paid under either option: the discovery shape must be unmisreadable.

Execution: domain:services lane, S. Re-measure /discovery on today's origin/main first (triage did not reproduce the 2026-09-03 showcase reading); pin the retraction (realtime entry enabled: false with no mounted surface; the predicate definition under test); update the discovery docs line. Clause-②: yes (the published discovery payload changes what it says for realtime) ⇒ needs:contract-review on the PR. Changeset: the package that owns the discovery entry, minor with a note (a client that keyed on enabled: true to subscribe was subscribing to nothing; it now sees false). Cross-link objectui#7249 so the bell card knows the answer is "poll".

State transition, same stroke: needs-user-decision → pm:queue. priority:p2 · domain:services unchanged. Ledger: director seat post #12708, batch #38.

---

Generated by Claude Code

[os-warren]

Correction to the ruling comment above (5542632689): the director session id is session_01LsEjuNMPitCHwEfYftZ1um (typo in the last three characters there). The ruling, provenance and state transition are unchanged.

---

Generated by Claude Code