Auto-sync: 2026-04-20 16:01
This commit is contained in:
36
wiki/concepts/Workflow-Architecture.md
Normal file
36
wiki/concepts/Workflow-Architecture.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
title: "Workflow Architecture"
|
||||
type: concept
|
||||
tags: [workflow-design, systems-design, process-engineering]
|
||||
sources: [specialized-workflow-architect]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Workflow Architecture 是一种把系统行为建模为工作流树的方法:先发现入口,再定义每一步的成功条件、失败分支、恢复动作、可观察状态和清理责任。
|
||||
|
||||
## Core Principles
|
||||
- 先发现,再设计
|
||||
- 先 happy path,再分支
|
||||
- 每个步骤都必须有 timeout
|
||||
- 每个失败都必须有 recovery path
|
||||
- 每个资源都必须进入 cleanup inventory
|
||||
- 每个交接都必须有明确 contract
|
||||
- 每个 spec 都必须接受现实验证
|
||||
|
||||
## Key Building Blocks
|
||||
- Workflow Registry:系统中所有工作流的权威清单
|
||||
- Handoff Contract:系统边界的 payload / response / timeout / recovery 定义
|
||||
- Observable States:客户、操作员、数据库、日志的状态定义
|
||||
- ABORT_CLEANUP:失败后的逆向销毁流程
|
||||
- Reality Checker:将 spec 与实际实现对齐的验证步骤
|
||||
|
||||
## Related Entities
|
||||
- [[Workflow Architect]]
|
||||
- [[The Agency]]
|
||||
|
||||
## Related Concepts
|
||||
- [[Claude Skills]]
|
||||
- [[Process Optimization]]
|
||||
- [[AI-powered Runbooks]]
|
||||
- [[Document Generation]]
|
||||
Reference in New Issue
Block a user