wangsli/hyb-oa
1
0
派生 0
代码 工单 合并请求 工作流 8 软件包 项目 发布 百科 活动

OMAT1 补充域级能力对标矩阵

浏览代码
这个提交包含在：
wangsli
2026-05-23 17:59:53 +08:00
父节点 eac650de8b
当前提交 037255ba30
共修改 5 个文件，包含 23 行新增和 3 行删除
下载 Patch 文件 下载 Diff 文件 展开所有文件 折叠所有文件
.agents/skills/hyb-oa-delivery/SKILL.md
+1 -1
查看文件
@@ -29,7 +29,7 @@ Read only what is relevant:
- ASSET1 is the current unified asset registry lane after OAOPS1: reuse the existing asset module for fixed assets plus electronic document/system/repository/backup asset metadata. Number families are `FA-YYYY-NNNNNN`, `EA-DOC-YYYY-NNNNNN`, `EA-SYS-YYYY-NNNNNN`, `EA-REPO-YYYY-NNNNNN`, and `EA-BKP-YYYY-NNNNNN`; `VER-NNNNN` is historical lookup only. `EA-ACC` is deferred: never store passwords, token, Secret, private keys, source bundles, full config, confidential document bodies, complete local paths, sensitive quotes, bank statement originals, or raw invoice images in OA, repo docs, chat, or reports. Git remains the source of truth for code; OA only stores repository metadata and responsibility. Historical company directory imports may only use redacted metadata from `00_保密索引`, default dry-run, with sensitive text/path guards.
- OSMOKE1 is the current OA-only smoke account governance lane after ASSET1D/OAOPS1 blockers: do not request more Enterprise WeChat accounts just to test OA-primary reimbursement/assets/finance/AP/contracts/permissions. Enterprise WeChat smoke accounts remain for HR/attendance evidence; admin/finance/hr/ceo OA regression accounts are OA-only smoke accounts and may be active in OA without WeCom binding. Use `npm run repair:oa-only-smoke` from `server/` for dry-run first; apply requires `--apply` plus `OA_ONLY_SMOKE_REPAIR_APPLY=1`, must not reset passwords, print secrets, affect real employees, or write WeCom. `audit-wecom-oa-user-consistency` classifies env-listed, explicit allowlisted, or `SMOKE*`/`smoke-*`/test-named OA-only smoke accounts as `oaOnlySmokeExempted` so they are not archived as missing in WeCom; `run-oa-real-use-daily.sh` includes OA-only smoke readiness before asset/finance UI automation.
- OALAUNCH1 is the current final-enable gate after OAOPS1/ASSET1D/OSMOKE1: do not treat ASSET1D completion or `PASS_OA_REAL_USE_DAILY_READY` as final launch approval. Use `scripts/qa/run-oa-final-launch-readiness.sh` to aggregate evidence only; it must not create business data, execute payments, write WeCom, reset/restore the production DB, print secrets, or mark final launch ready without real business closeout, 7-day stabilization, permission matrix acceptance, backup/restore drill evidence, data-governance/training acceptance, and Day 7 Go/No-Go. Valid conclusions are `PASS_OA_LAUNCH_READY`, `PASS_WITH_FINDINGS`, `PAUSED_MANUAL_CONFIRMATION`, and `SKIP/BLOCKED_BY_EXTERNAL_CONFIG`. Permission or backup/restore fixes require read-only reviewer review before launch acceptance.
- OMAT1 is the current maturity-gap review goal after OALAUNCH1: use `issues/2026-05-23_17-20-00-oa-maturity-gap-review-v1.csv` as the reviewable ledger for every problem or suggestion. It includes domestic benchmark sources, the small-team rule that maturity means controlled operation before feature breadth, explicit adopt/defer/reject decision回填, and a need for a concise evidence view. Follow the MAGI cycle wording as audit structure only: review/evaluate first, record or solve bounded evidence gaps second, then prioritize direction. Do not implement OMAT1 suggestions until the user chooses adopt/defer/reject and a proper Issue CSV exists for the adopted work.
- OMAT1 is the current maturity-gap review goal after OALAUNCH1: use `issues/2026-05-23_17-20-00-oa-maturity-gap-review-v1.csv` as the reviewable ledger for every problem or suggestion. It includes domestic benchmark sources, a domain capability comparison matrix in the manual trial-run report, the small-team rule that maturity means controlled operation before feature breadth, explicit adopt/defer/reject decision回填, and a need for a concise evidence view. Follow the MAGI cycle wording as audit structure only: review/evaluate first, record or solve bounded evidence gaps second, then prioritize direction. Do not implement OMAT1 suggestions until the user chooses adopt/defer/reject and a proper Issue CSV exists for the adopted work.
- WEGOV1 changes the current WeCom route to "Enterprise WeChat owns mature HR/attendance flows; OA stores self-owned history, audit, entry, messages, and emergency fallback." Treat four domains explicitly: WeCom-owned domain is check-in, leave, missed punch, outing, overtime, leave balance, and HR assistant; OA-owned domain remains reimbursement, procurement, contracts, projects, payments, invoices, bank receipts, sensitive attachments, and operating audit; OA archive domain stores WeCom business history, full external keys, and necessary snapshots; OA emergency domain is manually enabled only when WeCom is unavailable. Do not assume a full isolated WeCom sandbox; use the controlled test domain `SMOKE002 -> SMOKE101`, `OA-POC` templates, low-risk approvals, synthetic tests, public live runners, and limited real-device confirmation. WARCH1 now supplies the minimum leave/missed-punch archive implementation, WARCH2 supplies the formal read-only history query surface, and WROAD2 supplies controlled ops daily checks. Do not start deep mirror until WROAD2-CLOSEOUT, WROAD2-BIZ1, WAPPR1, WRULE1, WAUTO1/WEXT1LD, WFULLSMOKE1, WTCLOSE2, WEXT1-FORMAL, WREAL1 question gates or explicit approval, and the mirror stage's own contract are complete.
- For reimbursement, invoice, OCR, duplicate invoice, or attachment work, read `docs/报销发票附件规则.md` and `references/reimbursement.md`.
- For local/WeCom/public trial-run, OCR runtime, Caddy, or DB drift work, read `docs/试运行与自动化验证手册.md` and `references/trialrun.md`.
docs/trialrun/人工试运行报告.md
+19
查看文件
@@ -622,6 +622,25 @@ Go 结论边界：
最新只读证据：`artifacts/qa-flow/oa-final-launch-readiness-20260523-174759/summary.json`，结论 `PAUSED_MANUAL_CONFIRMATION`，open gate 仍集中在 OAOPS1-3/4/5/6 与 OALAUNCH1-3/4/5/6/7。
## OMAT1 域级能力对标矩阵
本矩阵用于把国内主流 OA/协同/低代码/财务/资产/HR 系统的常见能力域，映射到 hyb-oa 当前证据和缺口。参考来源只作为能力域参照，不代表要照搬大型套件复杂度。
| 能力域 | 国内成熟系统常见能力 | hyb-oa 当前证据 | 差距与建议优先级 |
| --- | --- | --- | --- |
| 门户/工作台 | 角色首页、待办、消息、移动入口、组织入口 | PC/移动/企微入口和 OAOPS1 每日巡检已有基础；移动矩阵和真机反馈有历史证据 | P1：7 天真实使用后按员工、审批人、财务、管理员高频路径做菜单降噪；不作为 P0 阻断 |
| 流程/表单 | 审批流、表单配置、转交、催办、数据权限 | OA 审批、workflowDefinitions、approvalRules、催办和通知已具备；企微 HR/考勤审批由企业微信主办 | P1：只做轻量配置台；复杂 BPM 和审批设计器继续冻结 |
| 报销/财务费控 | 发票/OCR、报销审批、付款批次、回单、AP、月结交接 | PDF OCR、付款批次、银行回单、AP 导出和代账交接 SOP 已有证据 | P0：补 1 条真实报销到付款/AP 闭环；P1：做一次月结/代账交接演练 |
| 采购/费用 | 采购申请、费用审批、供应商、报价、验收、付款关联 | 采购/费用申请和项目/合同关联有模块基础 | P0：补 1 条真实采购/费用闭环；P2：供应商准入、询比价和评价后置 |
| 合同/项目 | 合同台账、归档位置、项目关联、到期提醒、履约义务 | 合同台账、项目和关联能力已有；涉密正文线下归档边界已固定 | P0：补真实合同台账和权限抽样；P1：增强到期/履约提醒 |
| 资产台账 | 固定资产、电子资料、系统、仓库、备份、领用盘点处置 | ASSET1D 已完成 FA/EA-SYS/EA-REPO/EA-BKP 试录和 3 条 EA-DOC 导入 | P1：补真实资产领用/盘点/备份验证；不做 EA-ACC 凭据资产 |
| HR/考勤 | 组织、员工、假勤、打卡、补卡、外出、加班、假期余额 | 企业微信主办 HR/考勤；OA 已有留存、归档、审批链校验和正式模板测试号证据 | P1：OA 正式启用稳定后再问 WREAL1；HR 深镜像和应急接管后置 |
| 移动/企微触达 | 移动 Web、企业微信入口、消息、deeplink、审批可读性 | 企微消息、deeplink、移动矩阵和审批可读性均有阶段证据 | P1：稳定期记录真实用户体验；自动截图不能替代真机反馈 |
| 集成/开放边界 | ERP、银行、税务、电子签章、连接器、开放 API | 当前明确 ERP、银行流水导入、真实支付直连、图片 OCR 等冻结；OA 以导出和人工上传为主 | P2：继续冻结深集成；如重启也先做只读/导出/人工上传 |
| 数据安全/审计/运维 | 权限矩阵、审计、备份恢复、SLO、日志、问题处理 | 审计、/ready、每日巡检和手册已有；OALAUNCH1 显示权限矩阵、备份恢复和 7 天稳定化缺证据 | P0：权限负例、备份恢复演练、数据治理培训和 Go/No-Go 必须先闭合 |
参考资料入口：泛微 e-cology/e-office、致远 A8、钉钉宜搭、飞书审批/假勤、金蝶精斗云/云星辰、用友 BIP/畅捷通等官方资料；OMAT1 仅取其能力域和控制点作为审查基线。
## 历史恢复
需要追溯 R70-R91 的详细流水时，使用：
docs/文档事实源状态矩阵.md
+1 -1
查看文件
@@ -143,7 +143,7 @@
| `MANUAL-EMPLOYEE` | `docs/员工快速上手.md` | 操作手册 | 员工手册 | `CURRENT` | product | `R7E,WFOC,DBWFOC,WFDG,ASSET1,OALAUNCH1` | 人工验收 | none | 2026-05-23 | `rg` | low | 员工侧使用说明，HR/考勤优先企业微信，采购/合同/财务仍在 OA；补充统一资产台账、电子资产、涉密资产可见边界和 OALAUNCH1 收口期问题反馈口径 |
| `R7-DRAFT` | `docs/trialrun/R7扩大试运行草案.md` | 草案 | R7 准备材料 | `DRAFT` | product/qa | `R7E` | R7EP 报告 | none | 2026-05-13 | `rg` | medium | 不代表当前 R7E 执行状态 |
| `OPS-RUNBOOK` | `docs/trialrun/OPS7运维交接Runbook.md` | 运维草案 | OPS 准备材料 | `DRAFT` | ops | `OPS8,QAOPS8` | 只读检查 | none | 2026-05-13 | `rg` | medium | 不代表恢复演练已执行 |
| `TRIAL-REPORT` | `docs/trialrun/人工试运行报告.md` | 证据材料 | 试运行证据入口 | `EVIDENCE` | qa | `R7EP,OPS8,QAF8,WOUA,WAPI,WOUAFIX,WRV1,WRA1,WMSG1,WAPC1,WAPC2,WAPC2F,WAPC2FLIVE,WCBK1,WEGOV1,WROAD2,WARCH3,WCHECK1,WEXT1,WOPS1,WROAD2C,WROAD2B,WAPPR1,WAUTO1,WEXT1LD,WFULLSMOKE1,WTCLOSE1,WRULE1,WTCLOSE2,WREAL1P,ASSET1,OALAUNCH1,OMAT1` | artifacts/qa-flow | none | 2026-05-23 | `rg` | medium | 只证明发生过；记录 WAPC2FLIVE live 样件、WCBK1 真实回调事件、企微路线证据、WTCLOSE2 测试号最终收口、WREAL1 准备、ASSET1 统一资产台账、OALAUNCH1 最终启用门禁和 OMAT1 成熟度验收摘要；不直接放行深度镜像或最终正式启用 |
| `TRIAL-REPORT` | `docs/trialrun/人工试运行报告.md` | 证据材料 | 试运行证据入口 | `EVIDENCE` | qa | `R7EP,OPS8,QAF8,WOUA,WAPI,WOUAFIX,WRV1,WRA1,WMSG1,WAPC1,WAPC2,WAPC2F,WAPC2FLIVE,WCBK1,WEGOV1,WROAD2,WARCH3,WCHECK1,WEXT1,WOPS1,WROAD2C,WROAD2B,WAPPR1,WAUTO1,WEXT1LD,WFULLSMOKE1,WTCLOSE1,WRULE1,WTCLOSE2,WREAL1P,ASSET1,OALAUNCH1,OMAT1` | artifacts/qa-flow | none | 2026-05-23 | `rg` | medium | 只证明发生过；记录 WAPC2FLIVE live 样件、WCBK1 真实回调事件、企微路线证据、WTCLOSE2 测试号最终收口、WREAL1 准备、ASSET1 统一资产台账、OALAUNCH1 最终启用门禁、OMAT1 成熟度验收摘要和域级能力对标矩阵；不直接放行深度镜像或最终正式启用 |
| `FBA-AUDIT` | `docs/trialrun/R7E后功能边界审计.md` | 证据材料 | R7E 后功能边界审计 | `EVIDENCE` | product/dev/qa | `FBA,R7E,QAOPS8,P2T` | Issue CSV | none | 2026-05-15 | `rg` | medium | 只作为功能边界、P2 候选和 Issue 草案证据，不直接派工 |
| `HISTORY-MATRIX` | `docs/历史功能状态矩阵.md` | 历史材料 | 历史功能索引 | `HISTORICAL` | product | `DCL7` | git 历史 | none | 2026-05-13 | `rg` | low | 只追溯历史 |
| `OLD-IMPL-PLAN` | `docs/implementation_plan.md` | 已移除历史 | 早期实施计划 | `REMOVED` | product | `DCL7` | git history | none | 2026-05-13 | manual | low | 从 git 历史恢复 |
docs/文档索引.md
+1 -1
查看文件
@@ -238,7 +238,7 @@ R6 -> PC6 -> PA6 -> FL6 -> AP6 -> RI6 -> LP6 -> ME6/QG6 -> DG7/MRF7 -> MIA7 -> M
| 文档 | 用途 |
| --- | --- |
| [历史功能状态矩阵](./历史功能状态矩阵.md) | 轻量历史功能索引；旧大表从 git 历史恢复 |
| [人工试运行报告](./trialrun/人工试运行报告.md) | R6 后当前状态、关键证据索引和 OMAT1 成熟度验收摘要 |
| [人工试运行报告](./trialrun/人工试运行报告.md) | R6 后当前状态、关键证据索引、OMAT1 成熟度验收摘要和域级能力对标矩阵 |
| [R7E 后功能边界审计](./trialrun/R7E后功能边界审计.md) | R7E 后全端功能边界、P2 候选和后续 Issue 草案 |
| [试运行覆盖矩阵](./trialrun/试运行覆盖矩阵.csv) | 轻量覆盖摘要 |
| [项目级流程覆盖矩阵](./trialrun/项目级流程覆盖矩阵.csv) | `check-flow-coverage` 使用的最小流程矩阵 |
issues/2026-05-23_17-20-00-oa-maturity-gap-review-v1.csv
+1
查看文件
@@ -26,3 +26,4 @@
"OMAT1-24","用户采纳决策回填机制还不够显式","OMAT1 已记录问题和建议，但目前没有统一的回填口径来标记每条建议是 A 采纳、B 暂缓还是 C 不采纳；如果不补这个机制，成熟度审查容易变成开放式清单。","用户审查后，每条 OMAT1 建议必须在 Notes 或后续决策 CSV 中记录 A/B/C、理由、是否进入后续 Issue CSV、owner 和目标日期；未决项保持 TODO，不得自动实施。","受影响流程：成熟度台账 -> 用户评审 -> 决策回填 -> 后续合同；验证步骤：用户给出决策后，更新 OMAT1 或新建决策 CSV 并通过 validate_issues_csv.py。","manual|python3","TODO","TODO","TODO","issues/2026-05-23_17-20-00-oa-maturity-gap-review-v1.csv","[""OMAT1-21""]","优先级 P0；建议采纳。默认选项：A 采纳并转合同，B 暂缓观察，C 不采纳并记录理由；不能用 TODO 状态暗示已经同意开发。"
"OMAT1-25","成熟度证据缺少统一阅读视图","当前证据分散在 OMAT1、OALAUNCH1、OAOPS1、ASSET1D、artifact summary 和手册中；用户验收时需要一份按 P0/P1/P2 聚合的阅读视图，避免在多个 CSV 和 JSON 之间来回跳转。","在不新增业务功能的前提下，后续可生成 QA-only 脱敏成熟度摘要：列出当前成熟度判断、P0 open gates、P1/P2 建议、证据路径和人工决策选项。","受影响流程：证据收集 -> 成熟度摘要 -> 用户评审；验证步骤：先人工从 OMAT1/OALAUNCH1 形成摘要，若采纳再另建 QA-only 脚本合同。","manual","TODO","TODO","TODO","issues/2026-05-23_17-20-00-oa-maturity-gap-review-v1.csv;artifacts/qa-flow","[""OMAT1-24""]","优先级 P0；建议采纳手工摘要，脚本化可暂缓。摘要不得包含密码、token、完整账号、合同正文、银行流水、票据原图或原始 payload。"
"OMAT1-26","最低非功能基线仍需贴近真实使用复核","已有 /ready、最小构建、SLO 文档和每日巡检，但成熟系统还应确认附件上传/下载、PDF OCR、导出、付款批次、资产列表和审计查询在小团队真实数据量下没有明显性能或容量风险。","7 天稳定化期间至少记录一次关键页面响应、导出耗时、附件下载和 OCR 等待体验；若出现慢查询、超时或容量风险，进入 P1 修复合同。","受影响流程：真实使用 -> 页面响应/导出/OCR/附件 -> 日收口；验证步骤：OAOPS1 人工反馈 + 只读日志/报告抽样，不做压测公网、不制造大量数据。","manual|bash","TODO","TODO","TODO","docs/ops/SLO错误预算.md;docs/ops/非功能基线.md;scripts/qa/run-oa-real-use-daily.sh","[""OMAT1-5""]","优先级 P1；建议采纳为观察项。公司少于 10 人，不需要大型压测作为启用前阻断，但需要记录真实慢点。"
"OMAT1-27","国内能力对标需要落到域级矩阵","已有来源清单和 P0/P1/P2 摘要，但还需要按门户/流程/财务/合同/采购/资产/HR/移动/集成/安全运维等域，把国内成熟系统常见能力、hyb-oa 当前证据、差距和建议优先级放在同一张表，避免抽象讨论成熟度。","人工试运行报告包含域级能力对标矩阵；每个域只输出成熟度判断和建议优先级，不直接触发功能开发；用户可按域选择 A 采纳、B 观察、C 不采纳。","受影响流程：国内对标 -> 域级差距识别 -> 用户按域决策；验证步骤：rg -n ""OMAT1 域级能力对标矩阵|门户/工作台|财务费控|资产台账"" docs/trialrun/人工试运行报告.md。","manual|rg","TODO","TODO","TODO","docs/trialrun/人工试运行报告.md;issues/2026-05-23_17-20-00-oa-maturity-gap-review-v1.csv","[""OMAT1-22"",""OMAT1-25""]","优先级 P0；建议采纳为审查方法。参考泛微、致远、钉钉宜搭、飞书、金蝶、用友官方资料；只学习能力域和控制点，不照搬大型套件复杂度。"
1 ID Title Description Acceptance Test_Method Tools Dev_Status Review1_Status Regression_Status Files Dependencies Notes
26 OMAT1-24 用户采纳决策回填机制还不够显式 OMAT1 已记录问题和建议，但目前没有统一的回填口径来标记每条建议是 A 采纳、B 暂缓还是 C 不采纳；如果不补这个机制，成熟度审查容易变成开放式清单。 用户审查后，每条 OMAT1 建议必须在 Notes 或后续决策 CSV 中记录 A/B/C、理由、是否进入后续 Issue CSV、owner 和目标日期；未决项保持 TODO，不得自动实施。 受影响流程：成熟度台账 -> 用户评审 -> 决策回填 -> 后续合同；验证步骤：用户给出决策后，更新 OMAT1 或新建决策 CSV 并通过 validate_issues_csv.py。 manual|python3 TODO TODO TODO issues/2026-05-23_17-20-00-oa-maturity-gap-review-v1.csv ["OMAT1-21"] 优先级 P0；建议采纳。默认选项：A 采纳并转合同，B 暂缓观察，C 不采纳并记录理由；不能用 TODO 状态暗示已经同意开发。
27 OMAT1-25 成熟度证据缺少统一阅读视图 当前证据分散在 OMAT1、OALAUNCH1、OAOPS1、ASSET1D、artifact summary 和手册中；用户验收时需要一份按 P0/P1/P2 聚合的阅读视图，避免在多个 CSV 和 JSON 之间来回跳转。 在不新增业务功能的前提下，后续可生成 QA-only 脱敏成熟度摘要：列出当前成熟度判断、P0 open gates、P1/P2 建议、证据路径和人工决策选项。 受影响流程：证据收集 -> 成熟度摘要 -> 用户评审；验证步骤：先人工从 OMAT1/OALAUNCH1 形成摘要，若采纳再另建 QA-only 脚本合同。 manual TODO TODO TODO issues/2026-05-23_17-20-00-oa-maturity-gap-review-v1.csv;artifacts/qa-flow ["OMAT1-24"] 优先级 P0；建议采纳手工摘要，脚本化可暂缓。摘要不得包含密码、token、完整账号、合同正文、银行流水、票据原图或原始 payload。
28 OMAT1-26 最低非功能基线仍需贴近真实使用复核 已有 /ready、最小构建、SLO 文档和每日巡检，但成熟系统还应确认附件上传/下载、PDF OCR、导出、付款批次、资产列表和审计查询在小团队真实数据量下没有明显性能或容量风险。 7 天稳定化期间至少记录一次关键页面响应、导出耗时、附件下载和 OCR 等待体验；若出现慢查询、超时或容量风险，进入 P1 修复合同。 受影响流程：真实使用 -> 页面响应/导出/OCR/附件 -> 日收口；验证步骤：OAOPS1 人工反馈 + 只读日志/报告抽样，不做压测公网、不制造大量数据。 manual|bash TODO TODO TODO docs/ops/SLO错误预算.md;docs/ops/非功能基线.md;scripts/qa/run-oa-real-use-daily.sh ["OMAT1-5"] 优先级 P1；建议采纳为观察项。公司少于 10 人，不需要大型压测作为启用前阻断，但需要记录真实慢点。
29 OMAT1-27 国内能力对标需要落到域级矩阵 已有来源清单和 P0/P1/P2 摘要，但还需要按门户/流程/财务/合同/采购/资产/HR/移动/集成/安全运维等域，把国内成熟系统常见能力、hyb-oa 当前证据、差距和建议优先级放在同一张表，避免抽象讨论成熟度。 人工试运行报告包含域级能力对标矩阵；每个域只输出成熟度判断和建议优先级，不直接触发功能开发；用户可按域选择 A 采纳、B 观察、C 不采纳。 受影响流程：国内对标 -> 域级差距识别 -> 用户按域决策；验证步骤：rg -n "OMAT1 域级能力对标矩阵|门户/工作台|财务费控|资产台账" docs/trialrun/人工试运行报告.md。 manual|rg TODO TODO TODO docs/trialrun/人工试运行报告.md;issues/2026-05-23_17-20-00-oa-maturity-gap-review-v1.csv ["OMAT1-22","OMAT1-25"] 优先级 P0；建议采纳为审查方法。参考泛微、致远、钉钉宜搭、飞书、金蝶、用友官方资料；只学习能力域和控制点，不照搬大型套件复杂度。