81 lines
3.3 KiB
Markdown
81 lines
3.3 KiB
Markdown
---
|
||
title: "Automation Governance Architect"
|
||
type: source
|
||
tags: [agent, automation, governance, n8n]
|
||
date: 2026-04-20
|
||
---
|
||
|
||
## Source File
|
||
- [[raw/Agent/agency-agents/specialized/automation-governance-architect.md]]
|
||
|
||
## Summary
|
||
- 核心主题：自动化治理架构师，负责评估、审批和标准化业务自动化工作流
|
||
- 问题域：防止低价值或不安全的自动化实施，确保自动化投资回报
|
||
- 方法/机制：n8n 为主要编排工具的治理框架，包含决策框架、审批 verdicts、标准化工作流结构
|
||
- 结论/价值：通过 Governance-first 方法提升自动化质量、可靠性和可维护性
|
||
|
||
## Key Claims
|
||
- 决策必须基于价值而非技术可行性
|
||
- 每个推荐必须包含 fallback 和 ownership
|
||
- 无文档和测试证据不得标记为"done"
|
||
- 简单健壮优于巧妙脆弱
|
||
|
||
## Key Quotes
|
||
> "Do not approve automation only because it is technically possible." — 核心原则
|
||
> "No 'done' status without documentation and test evidence." — 完成标准
|
||
> "Every recommendation must include fallback and ownership." — 责任要求
|
||
|
||
## Key Concepts
|
||
- [[n8n]]：主要编排工具，n8n-mcp 提供 543 个节点访问能力
|
||
- [[ITSM（IT 服务管理）]]：自动化的服务治理背景
|
||
- [[Task Automation]]：任务自动化机制
|
||
- [[智能体工作流]]：以 n8n、Dify 为代表的工作流自动化平台
|
||
|
||
## Key Entities
|
||
- [[The Agency]]：开源 AI 智能体集合项目，Automation Governance Architect 是其 specialized agents 之一
|
||
|
||
## Connections
|
||
- [[n8n-mcp]] ← 使用 ← [[Automation Governance Architect]]
|
||
- [[Task Automation]] ← 治理对象 ← [[Automation Governance Architect]]
|
||
- [[ITSM（IT 服务管理）]] ← 隶属于 ← [[Automation Governance Architect]]
|
||
|
||
## Decision Framework（决策框架）
|
||
|
||
### 评估维度
|
||
1. **Time Savings Per Month**：月度时间节省，是否 recurring 和 material
|
||
2. **Data Criticality**：数据关键性（客户、财务、合同、排程记录）
|
||
3. **External Dependency Risk**：外部依赖风险（API/服务稳定性）
|
||
4. **Scalability (1x to 100x)**：可扩展性，retries、deduplication、rate limits
|
||
|
||
### Verdicts（审批结论）
|
||
- **APPROVE**：强价值、风险可控、架构可维护
|
||
- **APPROVE AS PILOT**：价值 plausibly 但需限制 rollout
|
||
- **PARTIAL AUTOMATION ONLY**：仅自动化安全段，保留人工 checkpoint
|
||
- **DEFER**：流程不成熟、价值不明确、依赖不稳定
|
||
- **REJECT**：经济性弱或运营/合规风险不可接受
|
||
|
||
## n8n Workflow Standard（工作流标准）
|
||
|
||
10 段结构：Trigger → Input Validation → Data Normalization → Business Logic → External Actions → Result Validation → Logging/Audit Trail → Error Branch → Fallback/Manual Recovery → Completion/Status Writeback
|
||
|
||
### Naming Convention
|
||
`[ENV]-[SYSTEM]-[PROCESS]-[ACTION]-v[MAJOR.MINOR]`
|
||
例如：`PROD-CRM-LeadIntake-CreateRecord-v1.0`
|
||
|
||
## Reliability Baseline（可靠性基线）
|
||
- explicit error branches
|
||
- idempotency 或 duplicate protection
|
||
- safe retries (with stop conditions)
|
||
- timeout handling
|
||
- alerting/notification
|
||
- manual fallback path
|
||
|
||
## Re-Audit Triggers（再审计触发条件）
|
||
- APIs 或 schemas 变更
|
||
- 错误率上升
|
||
- volume 显著增加
|
||
- 合规要求变更
|
||
- 出现重复人工修复
|
||
|
||
## Contradictions
|
||
- 尚未发现与现有内容的冲突 |