设计交付物发布

Pilot 控制

Control	Value
分类	WORKFLOW PILOT
名称	设计交付物发布（Design Deliverable Release）
Workflow ID	WF-DES-001 — PROVISIONAL
ID 规则	NOT APPROVED；本 ID 不建立企业级编号标准
Status	DRAFT
版本	0.1
Validation	NOT YET PERFORMED
Approval	NOT APPROVED
Golden	NO
本 Pilot 获授权的最高成熟度	DRAFT

本页是同一 Workflow identity 的中文表示。它是业务执行规范，不是自动化、界面操作说明、审批授权或 NocoBase 实现。

来源 Authority Map

草拟前已对来源分类。除非治理来源赋予业务 authority，否则 implementation behavior 只属于证据。

来源	分类	本页采用的 Authority	限制
docs/foundation/01-04	FROZEN	对 ERP Foundation V1 已覆盖架构、Relation、编号、Revision 与 integrity rule 具有 normative authority	不授权 workflow、approval、notification 或 evidence-blocking automation
contracts/phite-erp-foundation-v1.yaml	FROZEN	field、enum、Relation、Revision state 与 integrity 的共同 normative 机器合同	Status vocabulary 不定义 release authority 或完整流程
PHITE_ENTERPRISE_CODING_STANDARD_V1.1.md	APPROVED	冻结合同所选 active subset 内的 authoritative coding source	不定义 release gate
docs/foundation/05-deployment-and-verification.md	VERIFIED	Repository 记录的 deployment 与 metadata measurement evidence	不证明全部 runtime policy、当前 production state 或业务 acceptance
Handbook Foundation 页面	DRAFT	当前跨 Foundation 解释与明确缺口	不得覆盖冻结来源
DECISIONS.md 与 AI_CONTEXT_HANDOVER.md	REFERENCE	Decision routing、evidence boundary 与 unresolved-gap navigation	不是 Foundation amendment
AF-FOUND-001 Prompt.md	HISTORICAL	早期目标 chain 与字段的 provenance	不能建立当前 approval authority
.artifacts/nocobase-ui-builder/ 与当前 production behavior	UNKNOWN	不从其中推导业务规则	Apply、approval、acceptance 与 current state 均未验证
PHI-39 canonical brief	DRAFT	Workflow anatomy、Pilot constraint 与诊断方法	只授权 DRAFT，不批准缺失业务规则

Workflow Discovery Map

Business Object	Existing Rule	Source	Authority	Workflow Relevance	Confidence
Project	Engineering Deliverable 必须有一个 project_id；Project identity 与 domain status 相互独立	Relations contract；machine contract；ADR-010	FROZEN	必要发布 context；Project phase 不是 release authorization	High
Discipline	Deliverable 必须有一个 discipline_id；稳定 code 为 PRO、MEC、EIA	Numbering contract；machine contract	FROZEN	必要 identity 与 numbering dimension；有争议的 display label 不影响 eligibility	High
Engineering Deliverable	稳定 root，具有业务编号、Project、Discipline、responsible user、status 与可选 current-version pointer	Machine contract；ADR-007	FROZEN	稳定业务 identity 是 Deliverable root；candidate 与 release fact 记录在一个 Version；root status 是否同步仍为 OPEN	High
Deliverable Version	Version 属于一个 Deliverable；revision、revision_ordinal、prepared_by_id 与 status 已定义	Machine contract	FROZEN	Workflow 评估一个明确的 candidate revision	High
Revision	(deliverable_id, revision) 唯一；released history immutable；修改创建新 row	ADR-007；Relations contract；numbering contract	FROZEN	identity/history 前置条件与发布后保护	High
Engineering Review	Review 指向一个 Deliverable Version；stage 为 discipline_review 与 design_director_approval；decision 显式记录	Machine contract	FROZEN	Review evidence 结构存在，但必需 sequence 与最终 release authority 仍为 Open	结构 High；gate Low
Customer Confirmation	Customer confirmation 与 internal Engineering Review 分离	Relations contract；ENG-001 reference label	FROZEN / REFERENCE	不得静默视为内部 release approval	High
Controlled Document	Document identity/version/file 各自分层；Document 可引用 Engineering Deliverable	ADR-003；Relations contract	FROZEN	Design Release 在 controlled issue、transmission 或 customer submission 之前结束	High
Evidence	Evidence requirement/submission 使用 typed payload 与 formal Relation；禁止 generic soft link	ADR-004/005；Relations contract	FROZEN	Release evidence mapping 必须 typed；准确 evidence set 与位置未知	integrity High；mapping Low
Engineering Change	Change root/status 与部分 impact flag 已存在，但 frozen model 没有 Deliverable 或 Version Relation	Machine contract；Design 与 Change Foundation	FROZEN / DRAFT	只有附带 provenance 的显式 candidate reference 才可披露；不得从 Project/Discipline 推断 impact	Medium
Procurement Input	Procurement item 可引用 Engineering Deliverable 与 Document Version；适用时 PR 需要 traceability	Machine contract；coding standard	FROZEN / APPROVED	Procurement 是 downstream consumer，不是 release-governing Foundation	High
Freeze / Design Package / Checked By	完整语义、必需 record、gate 与 delegation 未建立	Design Foundation；Open Decision register	DRAFT / UNKNOWN	Owner decision 前不得作为 mandatory release input	对缺口存在性 High
Release authority	没有 approved source 指定谁可最终授权 Design Deliverable Release	Foundation scope exclusion；Design Foundation；UNK-007	OPEN / UNKNOWN	Mandatory Human Gate 必须 FAIL CLOSED	对缺口存在性 High

Mapping control	Status	Rule
Candidate-to-change mapping	OPEN	No approved Relation maps Engineering Change to a candidate Deliverable/Version. 显式提供的 reference 可作为附带 provenance 的 PROPOSED context 披露，但不能证明 impact。

Workflow 边界

IN SCOPE

• 将一个已识别的 engineering_deliverable_version 作为 release candidate 评估。
• 验证有依据的 identity、Relation、revision-history 与 metadata constraint。
• 汇集 existing review context，只披露附带 provenance 的显式 change reference，不推断 candidate impact 或 authority。
• 向 mandatory Human Gate 提交 release-eligibility decision。
• 在已授权的 Human positive decision 之后记录 release result 并保存 evidence。

OUT OF SCOPE

• 创建 Deliverable、执行设计开发或编写 candidate revision。
• 定义 Design Freeze、Design Package、Prepared/Checked/Approved RACI 或 approval delegation。
• Controlled-document issue、transmittal、customer submission/response、procurement issue、construction issue、handover、supersession、archive 或后续 revision。
• 任何 Agent skill、prompt-owned business rule、workflow engine、webhook、scheduler、approval automation、NocoBase change、schema change 或 runtime adapter。

UPSTREAM

Deliverable planning、design development、candidate-revision preparation，以及 accountable owner 所要求的 internal review activity。Scope/WBS 与 Work Package decomposition 仍由 OD-PRJ-001 决定，本页不静默将其变为前置条件。

Trigger boundary

当一个明确、已存在的 Deliverable Version 被显式提名为用于 eligibility assessment 的 release candidate 时，Workflow 开始。该 trigger 根据已支持的 submitted / under_review state 与 submitted_at INFERRED / PROPOSED；PHITE 尚无 approved canonical trigger event。

End boundary

成功结束条件是：已记录 authorized Human decision；选定 Version 已记录为 released 且未覆盖历史；release result/evidence 已通过 formal Relation 保存。Workflow 在 Document Control issue 或 downstream distribution 之前停止。由于 authorizing role 与准确 evidence mapping 未解决，production execution 当前必须停在 Human Gate。

DOWNSTREAM

Document Control 可随后创建或 issue controlled Document Version。Procurement、Construction、Customer、Supplier 等接收方可消费后续 controlled issue。Downstream consumer 不因消费 released content 而自动成为 governing Foundation。

Governing Foundation 与 downstream consumer

Relationship	分类	原因
Design Foundation	Governing	拥有 engineering content、Deliverable/Version、technical review context、Revision 与 Design Release concept
Document Control Foundation	Governing boundary	拥有 Design Release 之后的 controlled identity、issue、distribution、submission、response 与 delivery evidence
Project Foundation	Governing context	提供必需 Project identity；Scope/WBS decomposition 显式未解决
Engineering Change Foundation	Conditional governing context	只有 formal candidate mapping 或其他 approved evidence 建立 impact 后才治理 affected change；该 mapping 为 OPEN
Quality Foundation	Conditional constraint，不默认治理	仅当已有 authoritative project/design acceptance criterion 确实适用时参与；Quality Foundation 为 Concept/Draft
Procurement	Downstream consumer	可通过 formal requisition traceability 使用 released Deliverable/Document Version；不授权 Design Release
Construction / Customer / Supplier	Downstream consumers	可接收后续 controlled issue；distribution 不在本 Workflow 内

Draft Workflow Specification

每个 anatomy section 的三类标签用于防止 proposal 被误认为现有规则。

Trigger

SUPPORTED BY FOUNDATION： engineering_deliverable_versions 提供 submitted、under_review state 与 submitted_at field。Candidate 可通过稳定 Deliverable root 加明确 revision row 识别。

INFERRED / PROPOSED： HUMAN 将一个 existing Version 提名为 release candidate。提名只启动 eligibility assessment，不批准 release，也不创建新 Revision。

OPEN / UNKNOWN： Canonical triggering event、允许提名的 role，以及是否必须处于 submitted 或 under_review 均为 OWNER DECISION REQUIRED。

Inputs

SUPPORTED BY FOUNDATION： 当前可确认的 minimum input 为 Project、Engineering Deliverable root、Discipline、一个 Deliverable Version、prepared_by_id、current status、Revision identity、existing Engineering Review record，以及确实存在的 formally related controlled-document context。

INFERRED / PROPOSED： Release request 提供 candidate Version identifier 与 intended downstream use。Existing review record 被汇集为 eligibility packet。显式提供的 change reference 可附 provenance 单独列出，但不视为 affected-object Relation；不创造重复 Design Package root。

OPEN / UNKNOWN： Candidate-to-change mapping、Design Package、Checked By evidence、freeze baseline、mandatory customer confirmation、mandatory controlled Document 与完整 release-evidence template 均不是 approved input。

Preconditions

SUPPORTED BY FOUNDATION： Deliverable 必须保持有效 Project/Discipline/responsible identity；Version 必须属于该 Deliverable；Revision uniqueness 与 same-root current-pointer integrity 必须成立；正式生成的 business number 不得变化；released history 不得覆盖。

INFERRED / PROPOSED： Metadata check 确认 machine-contract required field 完整。Existing review decision 与任何显式提供的 change reference 连同 provenance 和 gap 一起呈现。任何 integrity check failure 都使 candidate ineligible。

OPEN / UNKNOWN： 没有 source 批准准确 review set、review order、checker independence、freeze effect、candidate-to-change mapping、change-clearance threshold 或 final release gate。这些 mandatory authority condition 因此 FAIL CLOSED。

Steps

SUPPORTED BY FOUNDATION： 以下 action 使用 existing business object 与 integrity rule，不改变 frozen Collection、Relation、status vocabulary、number 或 Revision rule。

INFERRED / PROPOSED： Minimum coherent business sequence 为：

Step	Business action	Actor Type	CAN EXECUTE	CAN AUTHORIZE	Result
1	将选定 Version 登记为 release candidate	HUMAN 或 SYSTEM	根据 Human request 记录提名	No	唯一明确的 candidate revision
2	验证 Deliverable、Project、Discipline、responsibility、number、Version ownership 与 required metadata	SYSTEM、AGENT 或 HUMAN	执行 deterministic validation 并报告 exception	No	Identity/metadata validation result
3	验证 Revision uniqueness、immutable-history protection 与 same-root current-pointer integrity	SYSTEM 或 AGENT	比较 governed record 并暴露 conflict	No	Revision-integrity result
4	汇集 existing Engineering Review 与 controlled-document context；只列出附带 provenance 的显式 change reference	AGENT 或 HUMAN	检索、分类并总结 formal record，不推断 Change impact	No	披露 mapping gap 的 evidence packet
5	评估 eligibility，将 candidate 分类为 eligible、correction required 或 hold	HUMAN，由 AGENT 或 SYSTEM 支持	应用 approved subset 并披露 open rule	无 final release authority	Eligibility recommendation
6	在 mandatory Human Gate 作出 decision	HUMAN	评审 packet 并记录 decision	仅在 owner 批准 business role 与 delegation 后为 Yes	Authorized release / return / hold decision
7	不覆盖历史地记录 authorized release result	SYSTEM 或 authorized HUMAN	在 valid gate 后记录 supported release fact	仅继承 Step 6 authority	Released Version record 与 timestamp
8	保存 release evidence 并提供 formal downstream handoff	SYSTEM、AGENT 或 HUMAN	记录/关联 evidence 并交付下一个 business boundary	No	Traceable result 与 Document Control handoff

OPEN / UNKNOWN： Step 6 的 organizational role、approved delegation、准确 review prerequisite、release evidence schema、root-status synchronization 与 authoritative record location 均为 OWNER DECISION REQUIRED。解决前，Step 6 不能授权 Step 7。

Decision

SUPPORTED BY FOUNDATION： Integrity violation 不得忽略；review decision 有显式 state；released history 受保护；customer confirmation 与 internal review 分离。

INFERRED / PROPOSED： 有意义的 branch 为：

candidate integrity valid?
  no  → HOLD，并纠正 governed record
  yes → required evidence complete under approved rule?
          no  → RETURN FOR CORRECTION 或 HOLD
          yes → authorized Human Gate granted?
                  no  → HOLD
                  yes → RECORD RELEASE 并 hand off

OPEN / UNKNOWN： “Required evidence complete” 与 authorized Human decision-maker 尚未被治理。Workflow 可以提出 eligibility recommendation，但不得从 status、reviewer title、customer response 或 technical capability 推断 approval。

Outputs

SUPPORTED BY FOUNDATION： Supported business result 是一个 history immutable 的 released Deliverable Version。只有 pointer 保持在 same Deliverable 内时，该 Version 才可成为 root current pointer。

INFERRED / PROPOSED： Output 分层如下：

Category	Output
Business Output	一个 Design Deliverable Revision 在 valid Human Gate 后被声明为 released
Record	Candidate identity、eligibility result、Human decision、Version released status、released_at 与 any same-root current-pointer update
Evidence	Validation result、引用的 review record、附带 provenance 的显式 change reference、Human decision evidence 与 downstream handoff evidence

OPEN / UNKNOWN： Deliverable root status 是否必须与 Version 同步、controlled Document 是否必须预先存在、canonical release-package form 均未知。

Evidence

SUPPORTED BY FOUNDATION： Review record 具有 reviewer、decision、comment 与 decision time；Version row 具有 preparer、Revision、state 与 release time；Typed Evidence 支持 formal payload，禁止 generic soft link。

INFERRED / PROPOSED： Critical action-to-evidence mapping 为：

Action	Result	Evidence	Foundation basis	Record location
Validate identity/revision	Candidate structurally eligible 或 held	Validation result 加 governed object identifier	ADR-004/007；Relations contract	UNKNOWN — proposed operational record
Review candidate	Review context 可见	Existing engineering_reviews record	Machine contract	记录的 Foundation deployment 中存在 NocoBase mapping；当前 authoritative instance 未验证
披露 supplied Change reference	不推断 candidate impact	Reference、source 与 provenance	Change root 存在；candidate Relation 为 OPEN	UNKNOWN — 仅为 proposed context
Authorize release	Release 或 hold 获授权	Human decision、actor、authority basis、time 与 comment	Authority principle；PHI-39 constraint	UNKNOWN — OWNER DECISION REQUIRED
Record release	Version released 且未覆盖	Version state、released_at、Revision identity 与 immutable history	ADR-007/008	Verified mapping 适用时为 engineering_deliverable_versions
Hand off	Downstream boundary 收到 traceable reference	Formal Deliverable/Document Relation 与 handoff record	ADR-003/004	Document Control release/issue mapping 批准前为 UNKNOWN

OPEN / UNKNOWN： Evidence template、signature requirement、retention rule、acceptance owner 与 validation/authorization/handoff 的 definitive System of Record 均未批准。

Acceptance

SUPPORTED BY FOUNDATION： Released Version 属于 intended Deliverable；Revision/business identity 保持稳定；不覆盖 released history；任何 current pointer 均 same-root；business fact、Document、Version、attachment、file 与 evidence 各自分层。

INFERRED / PROPOSED： 只有 candidate、validation result、applicable review context、任何附带 provenance 的显式 change reference、authorized Human decision、released state/time 与 downstream handoff 可作为一个 release result 被追溯时，completion 才可观察。

OPEN / UNKNOWN： Required review evidence、final authorizer、root/version state coordination 与 evidence location 未解决，因此 operational acceptance 为 PARTIAL，真实 release 前必须 FAIL CLOSED。

Failure Handling

SUPPORTED BY FOUNDATION： Integrity conflict、invalid Relation、duplicate Revision、cross-root current pointer、attempted history overwrite 与 prohibited generic link 是 supported failure category，必须拒绝。

INFERRED / PROPOSED： Missing required input、incomplete metadata、missing review context、rejected/changes-required review、显式提供但 unresolved 的 Change reference、missing Human Gate 与 recording failure 进入 RETURN FOR CORRECTION 或 HOLD；不定义 retry automation。

Failure	Classification	Handling
Invalid identity、Relation、Revision 或 immutable-history operation	SUPPORTED	拒绝 release path；保留 record；通过 governed Revision/Change behavior 纠正
Missing machine-contract input	SUPPORTED	Eligibility assessment 前退回纠正
Missing 或 adverse review context	PROPOSED，因为 required set 为 OPEN	Return 或 hold；不重新解释 decision
显式提供但 unresolved 的 Change reference	PROPOSED；candidate mapping OPEN	披露 provenance 并 hold 等待 owner assessment；不得从 Project/Discipline 推断 impact
Human authority unresolved 或 decision missing	SUPPORTED authority principle；role OPEN	在 Human Gate FAIL CLOSED
Evidence 或 System-of-Record write failure	PROPOSED；mapping UNKNOWN	不宣称 release completion；保存 error evidence 并 hold

OPEN / UNKNOWN： Escalation owner、service level、retry policy、emergency release、retrospective approval、cancellation 与 reopening 均未定义。

Human Gate

SUPPORTED BY FOUNDATION： Knowledge/capability 不授予 execution authority。AI 可以 check、compare、summarize 与暴露 gap，但 Design Foundation 明确 AI 不得 approve 或 release Revision。

INFERRED / PROPOSED： Eligibility assessment 与记录 released 之间必须存在 positive、attributable Human authorization。Gate 记录 actor、represented business role、authority basis、decision、time 与 comment。

OPEN / UNKNOWN： Approved organizational role、independence、delegation、substitution、threshold，以及 design_director_approval 与 final Design Release 的关系均为 OWNER DECISION REQUIRED。在 OD-DES-002 关闭前，Gate 必须 FAIL CLOSED，Pilot 不得作为 production release authority。

Actor 与 Authority Model

Capability ≠ Authority。 Actor Type 描述 action 如何执行；Business Role 描述 organizational accountability。本 Draft 不把执行绑定到具名 product 或 Agent framework。

Actor Type	CAN EXECUTE	CAN AUTHORIZE
HUMAN	在允许时 nominate、inspect、correct、assess、decide 与 record	仅限 accountable owner 批准的 role/delegate；当前 OWNER DECISION REQUIRED
AGENT	Validate metadata、compare Revision、assemble governed evidence、detect gap 与 prepare recommendation	没有 approval 或 release authority
SYSTEM	Enforce integrity、store governed fact、protect history 与 expose result	没有独立 business authority；只根据 valid authorized instruction 行动

Existing schema role/field，例如 responsible_user_id、discipline_lead_id、design_director_id、review reviewer_id 与 prepared_by_id，是 responsibility evidence，不是 final release authority 的证明。

Foundation Traceability

Workflow element	Foundation rule / decision	Source
Stable Deliverable 与 Version identity	ADR-007 root/version/current-pointer pattern	docs/foundation/01-architecture-decisions.md；machine contract
Project/Discipline ownership	Required owner Relation	docs/foundation/03-relations-and-integrity.md；machine contract
Revision integrity 与 immutable release history	Unique root/revision；released state immutable；修改创建新 row	Relations 与 numbering contract
Review evidence structure	两个 review-stage enum value 与显式 decision	Machine contract
Customer separation	Customer confirmation 不是 internal Engineering Review	Relations contract
Document Control boundary	Business fact、Document、Version、attachment、file、evidence 各自分层	ADR-003/004/005
Change context	Project/Engineering Change root 与 independent status 存在；没有 approved Relation 将 Change 映射到 candidate Deliverable/Version	Machine contract；ADR-010；Change Foundation Open model
Human authority gap	Workflow/approval excluded；Design release authorization open	Architecture scope；Design Foundation；UNK-007；OD-DES-002

System of Record

Handbook Markdown 的两种语言表示是本 Draft Workflow 的 canonical definition。NocoBase is not the canonical Workflow definition。

Information	Known mapping	Gap
Deliverable、Version、Review、Change、Document 与 Document Version fact	对应 Collection 存在于 frozen 87-Collection contract 与 recorded deployment	Current production state 与 business acceptance 未验证；Change-to-candidate mapping 未定义
Released Version 与 time	engineering_deliverable_versions.status / released_at	Authorized command 与 final release role 未定义
Eligibility validation	没有 approved business record mapping	UNKNOWN
Human Gate decision 与 authority evidence	没有 approved release-decision root 或 Evidence mapping	OWNER DECISION REQUIRED
Downstream handoff / Document Control issue	Design-to-Document Relation 存在；完整 issue/transmittal model 不存在	OD-DOC-001

本页不授权任何 Collection、field、workflow、plugin 或 production data change。

Open Decisions

Decision	Material gap
OD-ENT-002	Enterprise Workflow identity/numbering、ownership、validation、approval、versioning 与 Golden promotion
OD-DES-002	Trigger、mandatory review set、final release authority/delegation、root/version state coordination、evidence set 与 Design Release acceptance
OD-DOC-001	从 Design Release 到 controlled issue/transmittal 与 downstream evidence 的 boundary
OD-PRJ-001	Scope/WBS/Work Package/Deliverable decomposition；本页不将其设为 release precondition
OD-CHG-001	Change gate、threshold、authority 与 closure evidence，包括 post-freeze modification

轻微措辞与界面细节不会被不必要地提升为 Open Decision。

Pilot Evaluation

Diagnostic	Result	Reason
FOUNDATION COVERAGE	MEDIUM	Identity、Relation、Revision integrity、review structure、status vocabulary 与 boundary 较强；trigger、authority、acceptance 与 evidence mapping 不完整
RULE GAPS	Material	Release trigger、required review sequence、freeze effect 与 root/version coordination 为 Open
AUTHORITY GAPS	Material	Final release role、independence 与 delegation 未批准
EVIDENCE GAPS	Material	Required release evidence set、Human decision form、retention 与 handoff evidence 未批准
SYSTEM-OF-RECORD GAPS	Material	Core object 已 mapping，但 eligibility、Human Gate 与 handoff record 未知
TERMINOLOGY GAPS	Limited	“Release”“Freeze”“Design Package”“Checked By”缺少完整 governed semantics

Executability test

Question	Answer	Reason
Could a competent PHITE employee execute this Workflow correctly using the specification plus referenced Foundation rules?	PARTIAL	可准备和评估 candidate，但无法识别 approved final authorizer 或完整 acceptance/evidence rule
Could a future Agent execute the non-authority portions without embedding PHITE business rules inside its prompt?	PARTIAL	Governed identity/Revision check 已外置，但 review completeness、change clearance、evidence mapping 与 System of Record 未解决

Pilot Acceptance Assessment

Criterion	Result
Discovery first；Foundation traceability；boundary；one identity/two representations	PASS
Draft status only；actor model；Capability ≠ Authority；system boundary；no automation	PASS
Trigger；Inputs；Preconditions；Steps；Decisions；Outputs；Evidence；Acceptance；Failure Handling；Human Gate	PARTIAL — gap 显式并 fail closed
Bilingual parity 与 stable knowledge identity	PASS
No business-rule invention	PASS — proposal 与 unknown 明确分离

Pilot Maturity

DRAFT

本 Pilot 未经过 executed release validation、owner approval，也未提升为 Golden。

Next Validation Step

Exactly one smallest next action：accountable Design owner 针对一个 representative release case 决定 OD-DES-002，明确 final Human authorizer、mandatory review evidence 与 acceptance record，且不改变 frozen Foundation data contract。