SharePoint sync rulesSharePoint 同步规则

• Least-privilege tenant connection; encrypted credentials; webhook clientState checked; subscriptions renewed before expiry租户级最小权限连接；凭证加密；校验 webhook clientState；订阅到期前自动续期
• The webhook only triggers; the sync itself is idempotent on external ID + ETag / versionwebhook 只负责触发；同步本身按外部 ID + ETag / 版本做幂等
• Missed notifications recovered through a delta cursor — no daily full scan as the normal path漏通知通过增量游标补偿——不把每日全量扫描当常态
• Delete, move, rename, lost permission and revoked connection all become visible, operable states; portal downloads go through a controlled proxy删除、移动、重命名、权限丢失、连接撤销都形成可运营的同步状态；门户下载走受控代理

Acceptance验收

• Internal done, client accepted and agency approved can each be queried on their own and combined freely内部完成、客户接受、机构批准可各自查询、任意组合
• Any approval points to one file version and one decider任一批准都能定位到具体文件版本和决定人
• Duplicate webhooks never create duplicate versions or notifications重复的 webhook 不会产生重复版本或重复通知
• Normal changes visible within the ADR-07 target — provisionally P95 15 minutes — and recoverable from the cursor after an outage正常变更在 ADR-07 批准的时限内可见——暂定 P95 15 分钟——故障后可从游标补齐

Core entities核心实体

Client ── Contact
  │
  ├── Lead ── Deal ── Estimate ── Proposal ── SalesContract
  │                                            ├── ChangeOrder
  │                                            └── BillingSchedule
  │
  └── Project ── Phase / Milestone ── Task ── WorkOrder
                  │                     ├── TimeEntry / ExpenseEntry
                  │                     └── ResourceAssignment
                  ├── Budget / VendorBill
                  └── Deliverable ── Version ── Review / AgencySubmission
                                           └── TransmittalItem

SalesContract / BillingSchedule + approved Time / Expense
  └── Invoice ── Payment / Reconciliation

Sixteen state machines, from lead to transmittal — each with transitions, roles, preconditions, side effects, idempotency, compensation, notifications, audit and API error codes.16 个状态机，从线索到发文——每个都定义允许迁移、角色、前置条件、副作用、幂等、补偿、通知、审计与 API 错误码。

Conventions强制约定

• Every business table carries tenant_id, and it is part of unique keys and risky joins — not just a global scope业务表都带 tenant_id，并进入唯一约束和高风险关联——不只靠全局 Scope
• Queues, schedulers, exports, webhooks and console commands set and clear tenant context explicitly队列、定时任务、导出、Webhook 和命令显式设置、清理租户上下文
• Money in minor units plus currency; rates stored with their basis or a snapshot金额用最小货币单位加币种；费率保存适用依据或快照
• UTC storage; weeks, deadlines and report periods computed in the tenant's timezoneUTC 存储；按租户时区计算工时周、截止日和报表期间
• Document numbers from transaction-safe sequences — never count + 1单据编号用事务安全序列——禁止 count + 1
• Approvals and financial events are append-only; history is never overwritten审批和财务事件追加式记录，不通过覆盖字段抹去历史
• JSON only for low-coupling config and snapshots — never for ID lists that need integrity, queries or permissionsJSON 只用于低耦合配置和快照——不用于需要引用完整性、查询或权限判断的 ID 列表

Fix before the feature that depends on it在依赖它的功能上线前修复8

• R-03Money rounding mode unspecified — before M3 / M16 amount calculationsR-03金额舍入模式未指定——M3 / M16 金额计算开发前
• R-04Payment calls the gateway inside a DB transaction, no idempotency guard — before portal paymentsR-04付款在数据库事务内调用网关、缺幂等守卫——门户付款接入前
• R-07tenant_id IS NULL treated as super-admin — before any external identityR-07tenant_id IS NULL 被当作超管——开放外部身份前
• R-13Three estimate-approval paths behave differently — before proposal / contract conversionR-13三条估价审批路径副作用不一致——方案 / 合同转化链路前
• R-14Work-order states with no entry point — before task ↔ work-order mappingR-14部分工单状态没有入口——任务与工单状态映射前
• R-15Events and webhooks fired before commit — before new automationR-15事件 / Webhook 在事务提交前发出——新自动化上线前
• R-23Document numbers by count + 1 — before project / contract / transmittal numberingR-23单据编号用 count + 1——新项目 / 合同 / 发文编号启用前
• R-30Uploads without a tenant prefix — before portal uploads and deliverable attachmentsR-30上传路径缺少租户前缀——门户上传和成果物附件接入前

Test layers测试层级8

• Unit — money, rates, tax, transitions, scheduling scores, metric formulas单元——金额、费率、税、状态迁移、排班评分、指标公式
• Integration — DB constraints, queue retries, Graph / payment / accounting adapters, webhook idempotency集成——数据库约束、队列重试、Graph / 支付 / 会计适配器、Webhook 幂等
• Contract — OpenAPI, mobile compatibility, external driver samples契约——OpenAPI、移动端兼容、外部驱动样例
• Authorisation — same tenant other role, other client, other tenant, revoked grant — for every new resource授权——同租户不同角色、跨客户、跨租户、已撤销授权——每个新资源都覆盖
• E2E — proposal to project, time to invoice, deliverable to transmittal, portal approve and payE2E——方案到项目、工时到发票、成果物到发文、门户审批与支付
• Migration — anonymised snapshot backfill, reconciliation, roll forward and back迁移——匿名快照回填、对账、前滚与回滚
• AI evals — permission leaks, source correctness, extraction accuracy, reconciliation recall, injectionAI 评测——权限泄露、来源正确性、抽取准确率、差异召回、提示注入
• Non-functional — performance, concurrent numbering, duplicate callbacks, queue backlog, sync recovery非功能——性能、并发取号、重复回调、队列积压、同步恢复

Confirmed and kept · 2026-10-21已确认并保留 · 2026-10-217

• D1Engineering-consultancy positioning replaces the field-service positioning. Homepage, demo, materials and sample data switch; the field-service base is still reused underneath.D1工程咨询定位替代现场服务对外定位。首页、Demo、材料与示例数据整体切换；底层现场能力继续复用。
• D2SharePoint structure already exists; FieldsBrain adapts. No redesign of the client's site — permissions, mapping and exceptions still to confirm.D2SharePoint 已有结构，FieldsBrain 做适配。不重新设计客户站点——权限、映射和异常处理仍需确认。
• D3Agency submissions are recorded by hand. No agency API.D3机构报送仅人工记录状态。不接审批机构 API。
• D4Portal payments reuse the existing gateway. No new driver; billing and idempotency flows still to build.D4门户支付复用现有支付网关。不新建驱动；计费与幂等流程仍需补齐。
• D5The first release includes staffing suggestions. Explainable candidates, not globally optimal auto-scheduling.D5首版需要资源调度建议。交付可解释的候选人，不承诺全局最优自动排班。
• D6The pilot client is the firm that wrote the brief. Real flows and sample data at every phase gate.D6试点客户就是提出需求文档的工程咨询公司。各阶段用真实流程和样本数据验收。
• D7Eight disciplines, fixed for the pilot. Delivered as tenant-level seed data; a management UI can wait (see C1).D7专业分类试点固定 8 类。作为租户级种子数据交付；管理界面可延后（见 C1）。

Clarified in review审阅后的澄清7

• C1"Fixed 8, platform-level enum" → pilot default 8; the data model stays tenant-extensible.C1“固定 8 类、平台级枚举” → 试点默认 8 类；数据模型保持租户级可扩展。
• C2"Unapproved changes always blocked" → warning by default; soft or hard gate by tenant / project policy; exceptions audited.C2“未批准变更一律阻断” → 默认警告；按租户 / 项目策略软或硬门禁；例外需审计。
• C3"Metadata only, plus a full-text index" → ADR first; structured data only until authorised.C3“只存元数据，同时上全文索引” → 先做 ADR；未获授权前只检索结构化内容。
• C4"M2–M5 reused directly" → only estimates, signatures and payments are adjacent; CRM, proposals and sales contracts are new builds.C4“M2–M5 直接复用” → 只有估价、签名、支付等相邻能力可复用；CRM、方案、销售合同仍是新建。
• C5"About 20 / 94 new tables" → counts dropped; the schema inventory is the only measure.C5“新增约 20 / 94 张表” → 取消不可靠总数；以 schema inventory 为唯一口径。
• C6"12.5 people, 50 weeks, 1,240 days" → average 5–6.5 FTE, peak 10–12; re-baseline after phase 0.C6“12.5 人、50 周、1,240 人日” → 平均 5–6.5 FTE、峰值 10–12 人；阶段 0 后重基线。
• C7"M7 entirely conditional" → vendor and subconsultant bills with project cost move into M16 (REQ-6.5 / 7.2 / 7.8 / 8.5); only profiles, expiries and a subconsultant portal stay conditional.C7“M7 整体为条件项” → 供应商 / 分包发票与项目成本归集进入 M16（REQ-6.5 / 7.2 / 7.8 / 8.5）；只有档案、资质到期和分包门户保留为条件项。

Phase 0 hands over阶段 0 交付清单11

• Real process swimlanes with exception paths客户真实流程泳道图及异常路径
• Approved interpretation, priority, status and UAT case for every REQ ID每个需求 ID 的已批准解释、优先级、状态和 UAT 用例
• Current and target schema inventory, data dictionary当前 / 目标 schema inventory 与数据字典
• Role × object × action permission matrix角色 × 对象 × 动作权限矩阵
• State machines and approval-gate table状态机与审批门禁表
• Metric dictionary and sample-project reconciliation sheet指标字典和样本项目对账表
• ADRs: SharePoint, portal identity, financial source of truth, AI retrievalSharePoint、门户身份、财务事实源、AI 检索等 ADR
• Migration profile, pilot dataset, rollback plan迁移画像、试点数据集、回滚方案
• Executable API and integration spike results可执行的接口 / 集成 spike 结果
• Updated WBS, dependency graph, team allocation, P50 / P80更新后的 WBS、依赖图、团队分配和 P50 / P80 估算
• Acceptance script for the phase-1 demonstrable slice第一阶段可演示纵向切片的验收脚本