落实公司资料与 OA 运营映射规则（05-28-company-docs-oa-ops-mapping）

2026-05-28 21:26:01 +08:00
@@ -107,3 +107,51 @@ if (requiresDownloadReason(attachment) && !reason) {
 await prisma.auditLog.create({ data: buildDownloadAudit({ attachment, reason }) });
 return reply.send(stream);
 ```
+
+## Scenario: Company Documents And OA Collaboration
+
+### 1. Scope / Trigger
+
+- Trigger: mapping company electronic documents, policy files, operations
+  guidance, employee collaboration tasks or external-review materials into OA.
+- Applies to docs, specs, evidence, tasks, OA attachments, Enterprise WeChat
+  messages, AI/Codex-assisted processing and storage decisions.
+
+### 2. Contracts
+
+- OA is the operations control layer, not the full original-document library.
+- The controlled company document master keeps full originals, historical
+  packages and high-sensitivity materials.
+- OA may store indexes, business object links, status, responsibility, hash or
+  checksum summaries, archive-location summaries, review results and audit
+  evidence.
+- Necessary business originals may enter OA only through scoped business
+  attachment flows such as contract, reimbursement, purchase, payment, project
+  or policy workflows.
+- Employee collaboration, external review, generated reports, Enterprise
+  WeChat messages and AI/Codex work use redacted copies, aliases or summaries.
+- Do not build or describe a generic file center unless a Trellis task
+  explicitly reopens that architecture and defines permissions, audit, storage,
+  backup and retention rules.
+
+### 3. Storage Decision Defaults
+
+- Current V0 may keep authorized business attachments on the deployment
+  server, but it must not become a shared drive or full document mirror.
+- If storage is insufficient, prefer index-only records plus controlled offline
+  retrieval before moving high-sensitivity originals online.
+- Cloud object storage or controlled NAS/MinIO must be private, accessed by the
+  OA service account, and governed by OA permissions and download audit.
+- A home NAS can be cold archive, secondary backup or low-risk S3-compatible
+  trial storage; it is not the default production attachment store unless VPN,
+  private bucket, UPS, alerts and restore drills are in place.
+
+### 4. Forbidden Content
+
+- Full local paths to confidential directories.
+- Passwords, token, Secret, private keys, source packages and complete
+  configuration files.
+- ID-card, bank-card, payroll, social-security, tax and full bank-statement
+  originals in normal OA attachment areas.
+- Customer original material, sensitive quotes, contract bodies or signed
+  packages outside authorized business flows.
@@ -15,7 +15,7 @@

 ## Scope

-本任务只做公司资料与 OA 运营体系的脱敏映射、运营建议和后续路线规划。
+本任务先做公司资料与 OA 运营体系的脱敏映射、运营建议和后续路线规划；用户确认“能完成的都实施”后，将可立即落地的规则同步到现有 docs 事实源和 Trellis 稳定规约。

 纳入范围：

@@ -24,6 +24,7 @@
 - 业务指导：员工、负责人、财务、项目负责人、管理员如何用 OA 承接日常运营动作。
 - 流程联调：合同签署、采购付款、外包服务、入职、离职、项目验收回款、制度发布等场景如何串联 OA。
 - 后续开发建议：仅识别功能缺口，不在本任务直接改代码。
+- 可立即实施的文档/规约：管理员手册、员工快速上手、资产规约、合同附件规约、采购费用规约、报销附件规则和安全隐私 spec。

 ## Out of Scope

@@ -51,15 +52,16 @@

 ## Acceptance Criteria

- [ ] 已形成脱敏的资料类别到 OA 模块映射。
- [ ] 已形成资料管理、制度建设、业务指导三类运营建议。
- [ ] 已区分“现有 OA 可直接做”和“后续需要开发/优化”的事项。
- [ ] 已给出可执行的 0-4 阶段落地顺序。
- [ ] 已明确敏感资料边界和员工/Codex 使用红线。
- [ ] 已形成文件管理服务器的阶段性建议和准入条件。
- [ ] 已形成业务附件受控入库的状态、权限、下载和审计建议。
- [ ] 已形成跨业务附件矩阵，区分授权原文附件、脱敏协作附件和索引-only 资料。
- [ ] 已记录 inspected scope，但不泄露敏感文件名、完整路径或原文内容。
+- [x] 已形成脱敏的资料类别到 OA 模块映射。
+- [x] 已形成资料管理、制度建设、业务指导三类运营建议。
+- [x] 已区分“现有 OA 可直接做”和“后续需要开发/优化”的事项。
+- [x] 已给出可执行的 0-4 阶段落地顺序。
+- [x] 已明确敏感资料边界和员工/Codex 使用红线。
+- [x] 已形成文件管理服务器的阶段性建议和准入条件。
+- [x] 已形成业务附件受控入库的状态、权限、下载和审计建议。
+- [x] 已形成跨业务附件矩阵，区分授权原文附件、脱敏协作附件和索引-only 资料。
+- [x] 已记录 inspected scope，但不泄露敏感文件名、完整路径或原文内容。
+- [x] 已将可立即落地的运营规则同步到现有 docs 事实源和 `.trellis/spec/hyb-oa/security-privacy.md`。

 ## Test Plan

@@ -70,5 +72,6 @@

 ## Technical Notes

- 本任务是规划/审查任务，不启动实现阶段。
+- 本任务不改业务代码、不部署、不写公网真实业务数据。
+- 已实施的是文档和稳定规约治理：补充 OA 资料运营控制层、业务附件受控入库、索引-only、文件存储阶段性建议和员工使用红线。
 - 后续若决定新增“资料协作任务”“外发复核工作流”“制度台账”等能力，应另建或延续 Trellis 实施任务，并在编码前先给方案等待批准。
@@ -3,7 +3,7 @@
  "name": "company-docs-oa-ops-mapping",
  "title": "公司电子资料与 OA 运营映射审查",
  "description": "脱敏审查公司电子资料体系与 hyb-oa 运营、制度、台账、签收、复核和业务指导的配合方式。",
-  "status": "planning",
+  "status": "in_progress",
  "dev_type": null,
  "scope": "docs-analysis",
  "package": null,