Repository navigation
task: OBS — 解散 observability 过渡包并归位记录与展示 #413
Description
已确认实施方案：用户于 2026-11-12 11:35–11:36（北京时间）确认综合推荐，并要求快速、干净切换。
- 目的：这个第五顶层包不在 rfc: K/H/B 与 Apps 公开接口详细设计（最小交接与模块边界） #387 目标图里，按最终归属拆回，否则 R01 无法退役 K 壳。
- 迁入或删除：记录与对账回 H
harness/records；Dashboard / 时间线 / 模板进apps/views；knowledge_capture中的纯知识投影进 K。删除observability → catalog.BACKENDS、observability → _skill_selection.TASK_RELEVANCE：留 H 的部分不得导入 K，所需取值由 Apps 注入。不留转发壳。dashboard_workflow.py/profile_timeline.py须先补 D008 owner 再搬。 - 前置：K01、Publish standardized Apps run output #397。
- 验收：
observability/消失；固定记录下 CLI / 离线 Dashboard / live / trace 一致；H records 闭包不到达 K/Apps；overall 仍为 false。 - 明确不做：CLI 入口迁移、Publish standardized Apps run output #397 范围扩张、discussion: what trace evidence should InferRSI persist beyond per-run artifacts? #333/task: Dashboard 增强：每轮改动说明、动态 workflow 与耗时、测试进度 #345 增强。
合入后 overall isolation_complete 必须仍为 false。
关联架构总题 #387、Apps 设计 #371；#389 是当前清单与 observability 来源，#398 为已合入 H01，#397 保持纯 Apps 标准输出且只读不扩范围。
Activity
amy-why-3459 commentedon Nov 12, 2026
谢谢，这个包确实不在 #387 的目标图里，拆回最终归属是必要的。我核对了当前 main（
e2f4cd1e），补充几点：src/inferrsi/observability/knowledge_capture.py第 20 行是from .._skill_selection import TASK_RELEVANCE，第 74 行使用。按正文"所需取值由 Apps 注入"的做法，留在 H 的记录部分不能再拿到TASK_RELEVANCE，但目前写入 knowledge capture 的relevance_method取决于它。请在 PR 里说明注入点（Apps 在调用时传入），并用测试锁定迁移前后 capture 记录的这个字段不变。status:proposed，main 上还没有apps/。 Dashboard、时间线和模板要进apps/views，因此依赖这两项。请保持为显式前置。tests/check_profile_review.cjs等），可以直接复用作回归基线。dashboard_workflow.py/profile_timeline.py需要先补 D008 owner，这一步建议在 PR 描述里单列，先过 owner 评审再搬，避免和搬家混在一起审。docs: address K01 review comments and post-#338 isolation expectation
Merge branch 'main' into impl/obs-dissolve-2
style: sort imports in #384 view modules after the OBS retarget
Merge branch 'main' into impl/obs-dissolve-2
fix: restore Apps projection check in load_campaign_capture
Merge branch 'main' into impl/obs-dissolve-2
observability: present the OBS tree as a single commit on current main
Dong1017 commentedon Nov 15, 2026
@amy-why-3459 @zengchuang-hw — under the delegated architecture-coordination role, I adopt the joint five-entry D008 record for these two governing issues:
B01 delivers its implementation plus this shared decision metadata; OBS retains its implementation. This records architecture adoption, not independent implementation acceptance. Both issues retain their evidence requirements;
isolation_completeremains false.observability: dissolve the transition package into H records, Apps v…
Dong1017 commentedon Nov 15, 2026
Closing the bounded OBS migration slice delivered by PR #425, merged as
36440109.Harness owns factual records, Apps owns display/live decoration, and Knowledge owns pure projection under the D008 adoption. The joint architecture decision preserves the historical six-key layout without
retrievalfor readers supplying neither observation nor provenance, and retains the extended path otherwise. Format retirement requires a separate contract upgrade.Evidence includes final-head hosted checks and 362 passing exact-head Linux tests. Windows main-control evidence remains inconclusive. Overall
isolation_completeremains false.