brain/docs/adr/ADR-008-business-process-tooling.md

ADR-008: Business-process tooling (C10)

• Status: Accepted
• Date: 2026-05-17
• Deciders: Дмитрий

Context

The C10 «Бизнес-процессы (общее)» map section had zero tooling. C10 is the catch-all of bucket C — its work (modeling, automation, analysis of business processes) partly overlaps already-populated sections (C9 PM, E2 orchestration, A6 diagrams). A toolset is needed without duplicating those.

Decision

C10 adopts a hybrid toolset (Approach 3):

• operations plugin (operations@knowledge-work-plugins, Anthropic) — process documentation, change management, capacity planning.
• process-modeling skill — self-authored vendored skill: BPMN 2.0, process maps, RACI, state-machines. Renders via the mermaid skill.
• process-analysis skill — self-authored vendored skill: as-is discovery, bottlenecks, traceability, BP metrics.
• Five reuse cross-references (mermaid, architecture-patterns, CCPM, product-management, writing-plans) surfaced via NODE_SECTION_SECONDARY — no re-tagging of their home sections.
• n8n-mcp (workflow engine) is deferred: the portal stack has no n8n (the process engine is the Laravel queue); adopting n8n is an architecture decision with its own ADR. n8n-mcp is a reserved registry slot.
• C10 tools are non-UI → the business-process off-phase category, outside the PSR_v1 UI-pool.

Consequences

• Positive: C10 populated; modeling + automation + analysis covered with zero duplication of C9/E2/A6 tools.
• Risk: the two skills are self-authored — owned by the project, no upstream dependency (this is the mitigation, not a risk).
• Deferred: no workflow engine until n8n is adopted as infrastructure — accepted, this is the decision.

Enforcement

None — C10 tools are advisory; verified by use and code review.