Skip to content

task: OBS — 解散 observability 过渡包并归位记录与展示 #413

Closed

Description

@Dong1017

已确认实施方案:用户于 2026-11-12 11:35–11:36(北京时间)确认综合推荐,并要求快速、干净切换。

合入后 overall isolation_complete 必须仍为 false。

关联架构总题 #387、Apps 设计 #371;#389 是当前清单与 observability 来源,#398 为已合入 H01,#397 保持纯 Apps 标准输出且只读不扩范围。

Activity

  1. added
    kind:taskBounded delivery task with a delegated slice
    area:usabilityUsability and collaboration: issue navigation, templates, readable reports
    on Nov 12, 2026
  2. amy-why-3459 commented on Nov 12, 2026

    @amy-why-3459
    Collaborator

    谢谢,这个包确实不在 #387 的目标图里,拆回最终归属是必要的。我核对了当前 main(e2f4cd1e),补充几点:

    1. 要删除的 K 边已确认存在。 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 记录的这个字段不变。
    2. 前置 Publish standardized Apps run output #397 仍是 Draft,task: Apps 应用层详细设计与迁移计划(CLI / Python / Plugin) #371 仍是 status:proposed,main 上还没有 apps/。 Dashboard、时间线和模板要进 apps/views,因此依赖这两项。请保持为显式前置。
    3. "固定记录下 CLI / 离线 Dashboard / live / trace 一致",建议用一组固定的 campaign 夹具,生成迁移前后的离线 HTML 和 snapshot JSON,比对字节(或规范化后的 JSON)。PR Compare stage timings and inspect knowledge searches for each profile #401 刚加了不少 dashboard 渲染测试(tests/check_profile_review.cjs 等),可以直接复用作回归基线。
    4. dashboard_workflow.py / profile_timeline.py 需要先补 D008 owner,这一步建议在 PR 描述里单列,先过 owner 评审再搬,避免和搬家混在一起审。
  3. Dong1017 commented on Nov 15, 2026

    @Dong1017
    CollaboratorAuthor

    @amy-why-3459 @zengchuang-hw — under the delegated architecture-coordination role, I adopt the joint five-entry D008 record for these two governing issues:

    1. Benchmark owns sampling order, timing and artifact hashes; transport stays caller-injected.
    2. Harness owns the required snapshot port; Apps binds the infra implementation, with no Harness concrete default.
    3. Apps owns workflow display projections.
    4. Harness owns factual profile records, bounded single-trace overview and integrity/digest reads; Apps owns UI and live-route decoration.
    5. Apps owns pre-profile search display projections.

    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_complete remains false.

  4. Dong1017 commented on Nov 15, 2026

    @Dong1017
    CollaboratorAuthor

    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 retrieval for 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_complete remains false.

  5. zengchuang-hw commented on Nov 17, 2026

    @zengchuang-hw
    Contributor

    历史请求的独立实质检视,回应源键 comment:6887365381@2026-11-15T01:34:00Z(原请求定位)。Issue 保持 closed。本轮仅使用隔离后的原始需求/定位与固定源码,不把 decision 声明当作实施授权,也不重开任务。

    本轮独立核实的范围
    源码固定为 main 0311393c62330c041a01238dc86823b80e020561,不是历史交付时刻的验收证明。

    • 源树已无 src/inferrsi/observability 包。事实记录位于 harness/records,dashboard_workflow.py 位于 apps/views,profile_timeline.py 位于 harness/records;纯上下文投影函数位于 knowledge/context_projection.py。这能证明当前物理归属,不能证明历史负责人/接受决定已获授权。
    • 实际检查 apps/campaign.py:create_campaign:Apps 将 catalog.BACKENDS 作为 backends 参数注入记录层;capture_context 在 Apps 选择 TASK_RELEVANCE 并调用 reader,再把结果交给事实存储。没有把这两个 Knowledge 常量的选择权放进所检查的 Harness records 实现。
    • 独立 AST 检查 records 下 9 个模块,并解析相对/绝对静态 import 的可达闭包:10 个可达模块,未发现 Knowledge/Apps 模块。当前 Python import 扫描未发现旧 observability 导入。此检查不执行仓库代码,也不把动态导入、运行时回调或反射当作已覆盖。

    仍不能据此关闭的证据缺口

    1. 原始修订前合同和接受范围的可认证出处尚不完整。仅凭迁移后的代码不能确认所有权决定、拆分授权或完整原始验收矩阵。本轮不替维护者作这些决定。
    2. 未进行同一固定记录上的迁移前后 CLI/offline/live/trace 输出对照,没有实跑浏览器、live refresh、安装产物或真实宿主;目录消失和静态 import 闭包不等于行为等价。
    3. dashboard_workflow 与 profile_timeline 的当前归属已定位,但“搬迁前先指定负责人”属于历史治理事实,不能从路径反推。局部 records 闭包也不证明全仓 isolation complete;本轮不将总体隔离标为完成。
    4. 没有借此扩展 CLI 迁移、Publish standardized Apps run output #397 范围或 discussion: what trace evidence should InferRSI persist beyond per-run artifacts? #333/task: Dashboard 增强:每轮改动说明、动态 workflow 与耗时、测试进度 #345 增强;相关受保护的 benchmark: split the legacy run/evaluate chain into B, H, and Apps legacy (B01) #422/observability: dissolve the transition package into H records, Apps views, and K (OBS) #425 平台拒绝保持,本轮未请求这些对象或尝试替代访问。

    实际检查:仓库 ID/他人作者/ordinary Issue/closed 状态核验;固定 main 源码与 AGENTS/review skill 核对;上述实现函数、静态 import 与包路径检查;发表前仅按作者过滤核本人评论,未发现重复实质结果。未运行 pytest、模型、设备、付费调用或实验,未修改源码、权限、政策、Issue 状态或执行合并。

    结论:当前代码提供了 OBS 物理拆分、Apps 注入与 records 静态依赖边界的有限正面证据;历史授权和固定记录行为等价仍未证明。这是检视答复,不是整体需求验收或实施承诺。

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:usabilityUsability and collaboration: issue navigation, templates, readable reportskind:taskBounded delivery task with a delegated slice

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions